Code cleanup: Add comments to explain what different patterns match against

[maco]

A lot of the functions for analyzing code that are defined repeatedly with different headers, it can be hard to tell what semantically each one is for. They're mainly private functions, so they don't need @doc markers, but still, a comment on each saying what type of syntax gets matched there would be handy when we try to debug things in the future.