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

Annotations already signal destructiveHint=true and readOnlyHint=false, so the mutation and destructive nature are covered. The description adds context about fee-reversal rules and the wallet scope, but does not disclose side effects like irreversibility, partial refund behavior, or idempotency retry implications beyond the annotation.

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?

The description is a single focused sentence with no filler. The key verb and resource are front-loaded, and every phrase adds some context, making it economically written.

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?

Given this is a destructive mutation with no output schema and likely sibling ambiguity, the description is too thin. It omits prerequisites, idempotency behavior, refund scope, and any indication of what a successful refund returns. The existing annotations and schema do not compensate for these gaps.

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?

The input schema has no property descriptions, and the description does not clarify how paymentId, amountMinor, or idempotencyKey map to the refund operation. The property names and constraints carry most of the meaning, but with 0% schema coverage the description should have compensated and did not.

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 uses a specific verb ('Refund') and a clear resource ('a sale from the participant's owned seller wallet'), and it adds the mechanism of 'existing fee-reversal rules'. It is clear enough to distinguish the action from a generic payment tool, though it does not explicitly contrast with the similarly named sibling request_commerce_refund.

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?

No guidance is provided about when to call this tool versus alternatives such as request_commerce_refund, nor are exclusions or preconditions stated. The context signals include many commerce/payment siblings, making selection ambiguous without explicit direction.

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