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

Annotations already convey read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral context by explicitly stating the output will not fabricate a winner or composite score, which informs the agent's expectations beyond the 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 description is one concise, front-loaded sentence with no filler. It states the action, object, and a key behavioral constraint efficiently.

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?

The tool is simple, has one parameter, and annotations cover safety and idempotency. However, the description omits the exact meaning of targets and does not describe what the comparison output looks like, so an agent may need additional context to invoke it confidently.

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?

The only parameter, targets, has no schema description coverage, so the description carries the full burden of explaining it. 'Compare provider evidence' hints that targets refer to providers, but it does not clarify what form targets should take (names, IDs, URLs), leaving the agent to guess.

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 uses a specific verb and resource: 'compare provider evidence side by side.' It clearly distinguishes this tool from the sibling verification/checking tools by emphasizing side-by-side comparison, and the phrase 'without a fabricated winner or composite score' adds useful non-evaluative intent.

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?

The description implies the tool is for comparing provider evidence side by side, but it does not explicitly say when to use it over verify_provider or the check_* tools, nor does it mention any exclusions. Usage is inferable but not stated.

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