Just to be clear, I don't think verbosity means that documentation is better. Documentation is better when it gives you the information you need, and nothing more. That being said, I mostly think Go's documentation is better than Java's, and on par if not slightly better than C#'s. Here's a better example of what I mean, e.g. http://docs.oracle.com/javase/6/docs/api/allclasses-noframe.... vs. http://golang.org/pkg/
Granted, if you have no experience at all with the language--e.g. you haven't even taken the tour at http://tour.golang.org/--the documentation may be hard to read (what does "[]" mean, for example), but that's not the fault of API documentation, which rightly is clear and concise. Rather, that's the job for a comprehensive tutorial, which Go has: http://tour.golang.org/
http://golang.org/pkg/net/#example_Listener
---- begin example ---
package main
---- end example ---
which is a good example of a nonexistence of one good example.
There are no examples, the lifeblood of documentation, nor any notes about gotchas?
It's early days in the language so that's not at all bad, but claiming the documentation is better when it's clearly not is odd.
http://msdn.microsoft.com/en-us/library/b9skfh7s.aspx
Also C# and java are going to have tons of examples on SO, so the amount of examples and extra documentation available is incomparable.