Yes, I've seen it Clojure, where the documentation is extensive, giving great coverage to its standard library... but still haves you reading the source and searching the web for examples after reading the description, especially when speaking about macros (so... does this receive a vector? Does it take its arguments as a list, or what? A mixture of both?)
Racket goes full in the other direction, to a fault, even though it's much preferable.Racket's documentation is at times hard to wade through because it's so extensive. You have to scroll through the treatises and descriptions of options to find an example usage which will get you out quickly, but it's, for once, all there in the manual.