Hi Biterider!!
As far as I can tell, a lot of things have changed to help the programmer since the early days of ObjAsm.
Yes. There is a very interesting guide

But I used a very specific term wich is "documentation". And we were talking about library ObjMem. There is a lot of text in source code files, but
nothing in source code files is documentation. Perhaps you can debate with NASA laboratories, but I think that is correct.
Nobody like to write documentation, specially for free. But documentation is independent from code, sometimes follow source code structure, sometimes is similar, never is the same.
Additionally, there are some examples of increasing level of complexity and an API help file for RadAsm (see attached image). To better understand the object hierarchy and to read the object method documentation quickly, you have the OA_ObjExplorer in the project folder.
Maybe some tools are not perfect or incomplete, but I'm open to discuss changes to improve them. 
Nothing of that count like documentation nor help. A help is very close to documentation. Usually you know a help for extension *.hlp or *.chm and documentation for *.doc or *.pdf. Of course there are good and bad documentations and helps.
Some are "Smart things" that are usefull when you already know a lot about the subject. Then they are not so reliable.
The API files tool (they are not a help) depend on editor, and perhaps you have to modify the editor. I don't even know if I have API files in place

I tested only some Fearless API files for his libraries.
Other things that relly on editor are also problematics. I remember some years ago I tried to make a program with MasmBasic, wich don't have a help file but some smart thing in RichMasm, but finally I maked in PowerBasic, wich have a fantastic help!!
As you suggested, I will change the original approach and use UEFI procedures with a posfix. These procs will be aliased like the string procedures. 
Fantastic

Regards, HSE.