I have never used a template for this but as a guideline here is what you need:
Detailed requirements of what you expect the tool to do, included with these a priority or risk needs to be assigned to identify what you "must" have against what is would be nice to have. e.g. if you wanted to use the tool against applications developed in .net then the tool MUST be able to test .net products. If you have a budget this should also be included in your requirements.
Work with the vendors and the information they supply to see what requirements their tool will satisfy.
Short List the vendors and ask the them to demo their application.
From the demo short list the vendors again and do an on-site proof of concept on your own hardware against your own software - make sure that you are hands on with this to identify which software will work best for you.
I have not failed. I've just found 10,000 ways that won't work" --Thomas Edison