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

The description adds meaningful behavior beyond the annotations: the one-time 72-hour limit and the fact that the reservation remains held pending admin resolution. This complements the destructiveHint and idempotentHint annotations rather than contradicting them, even if it does not fully detail consequences of a rejected dispute.

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?

Two short sentences, front-loaded with the action and the most important constraint, and every word adds information. There is no filler or redundancy.

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 description captures timing and state effects well, but with three required parameters undocumented, no output schema, and no guidance about alternatives or prerequisites, the tool is not sufficiently complete for correct invocation. An agent would still be guessing about request_id and submission_id semantics.

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 only 25%, and the description does nothing to explain the required parameters submission_id, note, or request_id. An agent cannot determine what request_id refers to, what the note should contain, or which submission maps to the disputed rejection. The description completely fails to compensate for the schema gap.

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 action ('Dispute a rejection') and the domain context from the title, distinguishing it as a user-side action rather than an admin resolution tool. It does not explicitly name a sibling alternative, so it stops short of a perfect 5, but the verb and resource are unambiguous.

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 provides concrete usage constraints: it must happen 'once within 72 hours' and the reservation 'stays held until admin resolves it.' This gives an agent clear temporal and behavioral context, though it does not explicitly state when not to use it or name alternatives such as admin resolve tools.

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