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

Annotations only supply readOnlyHint=false, so the description carries the behavioral load and does add real value: the reason text is shown to the client (a user-visible side effect) and the call previews by default until confirm: true. It does not state whether a rejection can be undone or what status the claim moves to.

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 immediately followed by the side effect and the confirm gate. Nothing is redundant with the tool name or schema.

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 small confirm-gated mutation with no output schema, the description covers purpose, side effect, and execution gate adequately. The main remaining gap is irreversibility and post-rejection state, which matters for a destructive-sounding operation with no destructiveHint annotation.

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 33% and only confirm is documented in the schema, yet the description explains that reason is optional and client-visible, adding meaning beyond maxLength 500. id is left to the schema but is self-evident given the required-field name.

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?

Names a specific verb and resource (reject a direct-payment claim) and defines the claim condition (money not received), which an agent could not infer from the name alone. It is readily distinguishable from confirm_direct_payment_claim, though that sibling is never named explicitly.

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 parenthetical 'money not received' gives the triggering condition for rejecting rather than confirming, and the confirm-gating note tells the agent it needs a two-step call. It stops short of explicitly naming confirm_direct_payment_claim as the alternative action or stating when rejection should not be used.

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