cancel_order

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

The description reinforces the destructive nature (destructiveHint=true) and adds useful behavioral context such as requiring explicit user confirmation and a reason code. It does not contradict annotations and discloses the mutation effect without over-explaining.

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?

Three concise sentences, front-loaded with the core action, followed by usage guardrails. Every sentence adds critical guidance without redundancy.

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 description covers the main action and prerequisites well, but omits the optional `comment` parameter. Given the existence of an output schema, return values are not required, but the lack of comment guidance is a gap for a 3-parameter tool.

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?

With 0% schema description coverage, the description must compensate but only mentions reason_code indirectly and order_id implicitly. The `comment` parameter (optional, maxLength 500) is completely undocumented, leaving the agent guessing about its purpose or format.

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 'Cancel an order' with specific verb and resource. The name and context distinguish it from siblings like active_orders, confirm_order, etc.

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?

Explicitly states when to call ('only after user explicitly asks to cancel this exact order id') and includes a prerequisite to obtain reason_code from list_cancel_reasons and show it to the user. This provides clear guidance on alternatives and workflow.

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