Refund Order

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

With no annotations, the description bears the full burden of behavioral disclosure. It mentions optional entitlement revocation but omits side effects, irreversibility, and the confirmation flow implied by the 'confirm' and 'confirmation_token' parameters.

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?

A single, front-loaded sentence conveys the core action and an optional modifier with no redundant text. It is maximally concise while still carrying the primary purpose.

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 tool with five parameters including confirmation controls, the description is overly sparse. It does not explain the confirmation workflow, the impact of revoking entitlement, or how this refund differs from refund_external_transaction, leaving critical operational context missing.

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 description adds no meaning beyond the schema beyond the notion of revocation, which the schema already describes. Schema coverage is only 60%, and the description does not clarify the undocumented 'confirm' or 'confirmation_token' parameters.

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 the action (refund) and resource (order), and adds an optional behavior (revoking entitlement). It does not explicitly differentiate from sibling tools like refund_external_transaction, so it stops short of full sibling distinction.

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 given on when to use this tool versus alternatives such as refund_external_transaction or cancel_subscription_purchase. The description only states what it does, leaving the agent to infer the intended context and any prerequisites.

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