well, ok, but then there's the consistency concern. One may find it frustrating (tiring?) to constantly look for the description in the wrong place (ok, it will not be ALWAYS, but you got the the point). I would suggest discussing this with others and adding a line in HACKING file to decide where is the documentation to be stored. 

Please send a mail to mailing list on this matter - for some reason I can't. Since I intend to look into other files, I could as well implement an uniform style of comments in the source code. My personal experience was that a code base organized in a  consistent manner is a lot easier to grasp. And opencog has a large code base and not that many people contributing, so anything helping a prospecting programmer should be considered, me thinks. :)