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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description adds context beyond them: the one-vote-per-agent/version limit, that changes are logged, that no human approval gates the vote, and that votes are recorded opinions. It does not say whether a vote can be withdrawn or changed after casting, which is the main residual gap.

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?

Four short sentences with zero filler; the action and its precondition are front-loaded and each clause carries distinct information.

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 write tool with rich annotations and a fully documented schema, the description supplies the vote-governance semantics an agent needs: single-vote-per-version, logging, no human gate, and the opinion status of votes. Nothing required to invoke it correctly is missing.

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 description coverage is 100%, so the schema already documents record_id, version, reason, sources, and api_key thoroughly. The description only echoes 'version' and 'sources' in passing, adding essentially no syntax or format detail beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific action on a specific resource – 'challenge its credibility' after checking a version – which, combined with the name downvote_information, makes the operation unambiguous. It does not explicitly contrast itself with upvote_information, so sibling differentiation is implied by wording rather than stated.

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 a clear precondition for use ('After checking the exact version and sources'), which tells the agent when downvoting is appropriate. It stops short of naming the alternative tool for supporting a record or stating when not to vote at all.

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