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

Goes well beyond the annotations by disclosing the permission model, both distinct 409 version_conflict paths with their messages and ordering, that domain errors surface as tool errors, the exact success payload, internal-only persistence of review state, and the effect of later source edits on verification credit. Annotations only give idempotent/non-destructive hints; the description supplies the real behavioral contract.

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?

Front-loads purpose and permission, then errors, then return shape and replay caveats. It is dense and long for a tool description, with some overlap between the 'later source edits' and 'successful replay' caveats, but nearly every sentence carries operative 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 7-parameter, no-output-schema mutation tool, the description compensates by spelling out the success payload, the two failure modes, and the replay/edit interactions. Nothing an agent needs to invoke it correctly or interpret the receipt 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 coverage is 100%, so the baseline is 3, but the description adds genuine semantics the schema does not carry: the sequencing of the two conflict errors (correction version first, then target), the advice to read both records before retrying, and the op_key replay rules tied to retained authority and access.

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?

Opens with a specific verb pair and resource: 'Verify or revoke a correction to a record in the same thread.' It is clearly a review/state-change operation on a correction rather than a report or document edit, though it never explicitly contrasts itself with neighbors like review_report or moderate.

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?

States the authorization precondition precisely ('Only the corrected author or space owner may review, and never a correction revision they wrote') and the freshness precondition for new operations. It does not name an alternative tool or say when to prefer it over one, so it stops short of full when/when-not guidance.

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