Cancel order (refunds remainder)

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

Given no annotations, the description reveals the refund behavior ('unfulfilled remainder is refunded to the key's USD balance'). This adds context beyond the input schema, though it omits details like irreversibility or error conditions.

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 short, focused sentences with no filler. The critical information (cancellation and refund) is front-loaded, and the parameter usage is clearly stated.

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?

The tool has low complexity and no output schema, but the description fails to mention constraints like whether fully fulfilled orders can be cancelled or if partial cancellations are supported. The refund detail is helpful but leaves 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 single parameter 'orders' has 100% schema coverage with description. The description adds 'Pass orders as a list of order IDs', which reiterates the schema. No additional semantic information is provided 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?

The description clearly states the tool cancels orders and refunds the unfulfilled remainder, using a specific verb ('Cancel') and resource ('orders'). It distinguishes from siblings like 'create_order' and 'order_status' by focusing on cancellation and 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?

The description does not explicitly state when or when not to use the tool, nor does it compare with sibling tools. It implies usage via the verb 'cancel' but lacks guidance on scenarios like already fulfilled orders.

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