There's another trade-off / fine-line-to-walk possible here, informed by the principle of least surprise . So, when you document some example, which (to new readers) seems confusing, because it's "required" by the particular things in your example, you could choose to acknowledge the potential surprise by adding a short comment - something like "you might be surprised that these constants are in the UimaUtil class/interface, rather than the Tokenizer class/interface, but that's where those components define them!
The downside of adding things like this is that your documentation gets longer. And today's reader of documentation is probably impatient, and somewhat annoyed by longer docs.
There's things you can do with formatting to mitigate this kind of thing, like making it a "note", perhaps in slightly smaller font, so it's subordinate to the main "flow", visually.