Refund External Transaction

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that a refund is performed, with no mention of side effects, idempotency, permission requirements, reversibility, or constraints on refund timing/amounts.

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, front-loaded sentence with no filler or repetition. It states the verb, the target resource, and the clarifying qualifier in the most efficient way possible.

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?

Despite having an output schema and nested objects, the description remains too sparse for a sensitive financial mutation. It lacks guidance on how this differs from refund_order, what the refund object must contain, and what behavioral constraints apply. The schema covers parameter formats, but the description does not provide enough operational context.

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 description coverage is 100%, so the schema already documents all three parameters. The description itself adds no additional parameter-level meaning beyond identifying the refund object as containing refundTime plus fullRefund or partialRefund, which is already in 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?

The description uses a specific verb ('Refund') and a specific resource ('external (alternative billing) transaction'). The parenthetical clarifies what 'external' means, and this distinguishes it from the sibling 'refund_order', which targets regular orders.

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 implies this tool is for external/alternative-billing transactions, which provides some context for when to use it. However, it does not explicitly state when not to use it or point to alternatives like refund_order, leaving the selection decision largely to inference from the tool name.

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