First, interproscan / interpro2go,... You often only get the molecular function though (like this is a DNA binding protein, but you do not know what functional pathway it affects), as you are looking at protein domains/large families.
UniprotKB/Swissprot is better (curated protein database), but you don't have that many proteins available. You can do a tabular blast against UniprotKB and and retrieve GO codes using the GO Lead SQL database. Even better, you can query the go annotation evidence. Other protein databases may give you a name but no GO terms.
Last, but not least, you can try to scan the relevant HMMs in Eggnog (I am not sure if Trinotate do that).
http://geneontology.org/page/go-annotation-standard-operating-procedures could also be a start. Some consortiums are much more organized than others and have better annotations (http://www.wormbase.org/, not to name it). Some GO terms may be assigned a bit too hastily, keeping track of the source you used is a must.
Make no mistake, Trinotate is just a Perl wrapper around a SQL database that does the job of summarizing what you got from your searches of various databases, and can export it in a convenient format. I have a few bash scripts that do a much poorer job, but it is similar in spirit. Did I say Blast2GO (free version) is waaaaay slower than a direct search on your hard drive/nearest cluster, since it uses public servers?
I really like what they did in this paper on crocodiles: http://www.sciencemag.org/content/346/6215/1254449. In the functional annotation part of their Supplementary Materials, they explained how they proceed. Their annotation is easy to parse, they use clear codes and show their matches.
Not sure what you're getting at with Trinotate, all of these programs function in more or less the same way. It does assign eggNOG annotations.
Another option would be to map GO terms via PFAM hits.
My point is that Trinotate or Blast2GO are useful programs, which both build an annotation report after parsing the output of searches against third party sources. What I wanted to do is to introduce these ressources and some potential pitfalls.