What i meant to ask is, there is definitely no need for someone to document every possible aspect of a code with detailed example, heck not even feasible i would guess.
what i want to know is, how do i interpret the keywords.txt file?
i see this is fairly common, but i have no idea what the labels mean. no one actually complains about this.. so i thought im the one whos in the wrong.
There may be no need to provide a detailed example of every aspect. However, every function of an API should be documented. Tools like Doxygen exist, that when used correctly, can automatically generate a function summary document from annotated source code. It's common because people aren't paid to write the libraries, and often are not professionals who are used to producing documentation as a strict requirement of their job. Of course, it's feasible.
In this case, the main complexity is just a list of effects. An example is given to show how to use an effect, so there is not much difficulty in looking up the effect to see what it does, or simply trying it out. A description of each effect might be somewhat non-technical anyway, like "runs pink dots in one direction and yellow dots in the other on a blue background" or something like that. Really, how accurate or complete does that description have to be, in order to use it?
Complaining is silly, because as I said, it's free open source, why should anyone make changes to code just to make you happy when they aren't receiving any money for it? It's provided as-is, if you want something better, move on or fix it yourself.