create_refund

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

No annotations are present, so the description must disclose effects. It mentions payment methods and refund scope but does not state side effects on order state, permissions required, or restocking implications, leaving the agent under-informed for a mutation tool.

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 sentences, front-loaded with the core action, then a compact list of capabilities. No wasted words.

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?

Although the schema is well-described, the tool has 5 parameters and no output schema; the description lacks information about return values, prerequisites (e.g., order must be paid), and edge cases, making it only partially complete for a non-trivial refund operation.

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 descriptions cover all parameters and nested fields, so the baseline is met. The description adds broad capability language ('line items, shipping costs') that loosely maps to refundLineItems/shippingAmount but does not detail syntax beyond 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?

Description states 'Create a refund for an order' with a specific verb and resource, and enumerates supported dimensions (line items, shipping, payment methods), making the tool's role clear and distinguishable from sibling return/order-cancel tools.

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 explicit guidance on when to use vs alternatives like create_return or cancel_order; the 'refund for an order' phrasing implies post-order context but does not exclude or compare alternatives.

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