refund_payment

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It states the action but does not say whether the refund is irreversible, whether it mutates the transaction status, whether it requires special permissions, or what happens in error cases. This is a significant gap for a side-effectful payment operation.

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 sentence with no filler. Every word carries meaning, the core action is front-loaded, and the qualifying details ('full or partial', 'by transaction ID') are integrated efficiently.

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 mutation tool with no annotations and no output schema, the description is incomplete for an agent to invoke it reliably. It lacks usage context, behavioral consequences, return information, and error handling. While the schema covers parameters fully, the overall context is not sufficient for a refund operation with meaningful financial side effects.

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 already describes all three parameters, including the meaning of Amount as the full or partial refund amount. The description restates 'by transaction ID' and 'full or partial', which adds minimal value beyond the schema. With 100% schema coverage, the baseline 3 is appropriate.

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 states a specific action ('refund'), a resource ('payment'), and a scope ('full or partial') keyed by transaction ID. It reads as an unambiguous definition, but it does not explicitly distinguish itself from the sibling 'void_payment', which is a related but semantically different operation, so it falls short of full sibling differentiation.

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 gives no guidance on when to use this tool versus alternatives like 'void_payment', 'charge_payment', or 'auth_payment'. It implies the trigger (a transaction ID) but does not state the context, prerequisites, or exclusions that would help an agent choose correctly.

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