Cancel Order

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

The description states 'errors if already cancelled', which contradicts the idempotentHint=true annotation. Per guidelines, a contradiction scores 1. Otherwise, the description adds useful context about return format and 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?

The description is a single focused sentence with no waste, covering purpose, return value, and error conditions efficiently.

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 simple one-parameter tool without output schema, the description is complete: it explains what the tool does, what it returns, and error cases, and adds parameter source 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?

The description adds context beyond the schema by specifying that order_id comes from submit_order or today_orders/history_orders, helping the agent source the correct value.

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 ('cancel'), the target ('open order by order_id'), and the return value ('plain text order cancelled'). It distinguishes from sibling tools like submit_order and replace_order by specifying it's for open orders only.

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 implicitly says to use it for open orders and notes errors if already filled or cancelled, indicating when not to use. However, it does not explicitly mention alternatives like replace_order for modifying an order.

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