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

Annotations already cover idempotency and safety (idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds the key consequence that confirm causes the payment to count in balances while dispute never counts, which is real behavioral context an agent needs to choose an action.

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 tight sentences with the core action and outcome front-loaded, then the precondition. No filler.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety/idempotency profile. The description supplies role, effect, and precondition, leaving only failure/edge behavior unstated.

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 only 25%, with just idempotency_key documented. The description conveys the meaning of the 'action' values (confirm vs dispute effects), but says nothing about payment_id or the optional note. With low coverage it partially compensates for one parameter while leaving the others to the schema.

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 pair (confirm/dispute) and resource (payment), states the acting role ('as the receiver'), and spells out the divergent outcomes. An agent can distinguish it from record_payment or list_payments without opening the schema.

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?

Gives a clear precondition ('Only recorded payments can be confirmed or disputed') and the role context (receiver, not payer). It does not explicitly name record_payment as the prerequisite step, so the routing is implied rather than stated.

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