Go has interfaces that you implement just by having the methods, without declaring that you're implementing the interface (e.g. "implements" in Java). How well

Go has interfaces that you implement just by having the methods, without declaring that you're implementing the interface (e.g. "implements" in Java). How well does that work with tooling? For example, in Java, I frequently ask my tools, "Give me a list of classes that implement this interface," and I expect a fast and -- most important -- 100% accurate answer. My instinct is that Go's approach makes it tooling-unfriendly (a good chance of false positives, especially in large systems), but perhaps I'm missing something.