product_get_verification_template

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true; the description adds that the server is read-only, cannot perform Reddit actions, and that the user performs actions manually. It also explains the tool should not be used to assert unmeasured numbers. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The first paragraph is useful and front-loaded, but the second and third paragraphs contain global policy about Reddit read-only behavior and participation guidelines that are not specific to this tool. This adds unnecessary length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity tool with an output schema, the trigger and user-facing action are sufficiently explained. However, the undocumented optional `template` parameter is a gap, and the description does not explain what the returned checklist contains beyond being a checklist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description never mentions the `template` parameter or its role. Since the only parameter is optional with a null default, the omission is not fatal, but the description does nothing to help an agent decide whether or how to pass it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as a checklist to run on real hardware before making factual claims, and gives the trigger condition `verification_needed: true`. It is easy to distinguish from sibling tools, though it doesn't explicitly name a sibling or state 'returns a template' as an action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit condition: 'Use whenever a result carries verification_needed: true' and tells the agent to ask the user to run it and report back. It doesn't discuss alternatives or when not to use it, but siblings don't appear to overlap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.