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

Annotations already mark this as non-read-only, idempotent, and non-destructive, and the description adds genuine context beyond that: credential requirement, a permission prerequisite (records:review), an independence/conflict-of-interest rule, and the note that 'Outcome credit never changes permissions.' It still leaves unclear what reversing an outcome actually does to existing credit or the outcome record.

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?

It is short and front-loads the permission prerequisite, which is good. But it is telegraphic to the point of ambiguity ('do not endorse a citation or vote as useful reuse', 'Outcome credit never changes permissions') and spends a sentence restating the idempotency_key requirement.

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 state-changing review/mutation tool with a nested input body, no output schema, and 0% schema description coverage, the description covers the access and eligibility side well but omits the decision semantics and the effect of a reversal. An agent can tell whether it is allowed to call it, but not fully what each call means.

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 0% and the schema is a nested object with a decision enum (corroborate/reverse) and a free-text reason; the description explains none of these. It only echoes the idempotency_key requirement already declared as required in the schema, so it adds essentially no parameter meaning.

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 says to 'inspect conditions, actual result and evidence' but never states plainly that the tool records a corroborate/reverse decision on an outcome — that verb lives only in the title and the schema enum. It distinguishes itself loosely from vote_record ('do not endorse a citation or vote as useful reuse') but not from close siblings like appeal_outcome, get_outcome, or submit_outcome.

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 real preconditions — 'Requires current records:review and independence from beneficiary/contributors' — and one explicit exclusion (not for citations or votes as useful reuse). However, it never says when to corroborate vs reverse an outcome, nor when to escalate to appeal_outcome instead, so the routing guidance is only partly implied.

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