HeLLFox, what I'm asking for is a working example of how would setup the documentation. EG, we're using Natural Docs right now. If you think using a wiki would be better, create one and document a few functions to show us how you would envision it working.
Though as a note, I think Garry's documentation started out awful and has progressively gotten worse. He did no documentation himself and instead relied on the community to document his work... which is just an awful idea from the get-go. But, when he tried to be more regimented about documenting things himself, it turned out even worse. Or at least, I always find myself referring to the old wiki archives because they tend to be more accurate. Also, we have used a wiki for documenting in the past with very little success ourselves, but that was a very, very long time ago so I'm willing to give it another shot.
On UCL in particular, Natural Docs isn't working quite like you'd expect it to because of ND's limitations with Lua, but if you really needed to see all UCL functions you can do so by looking through the three UCL files (server, shared, client). It's not perfect, but our current documentation system beats out Garry's quite handily.