cancel_order

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

With no annotations provided, the description carries the full burden. It discloses the restocking behavior, which is valuable. However, it does not mention potential errors (e.g., if order is in an invalid state), irreversibility, or other side effects beyond restocking.

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, well-structured sentence that conveys the core action and a key behavioral detail. It is appropriately sized for the tool's simplicity (one required parameter).

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?

Given the simple tool (one param, no output schema), the description covers the basic action and a side effect. However, it lacks information about return values, error conditions, or prerequisites (e.g., order must exist). This leaves some gaps for an agent to handle.

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 'order_id' has 0% schema description coverage, so the description must compensate. The description does not elaborate on the parameter beyond what the tool name implies, leaving the agent to infer that it refers to the order to cancel. No constraints or format details are provided.

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) and the target (a pending/released order), and includes a specific side effect (restocking lines). This effectively differentiates it from sibling tools like 'get_order_status' or 'place_order'.

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 use for pending or released orders but does not explicitly state when not to use it or mention alternatives for other order states (e.g., held, shipped). Siblings like 'release_hold' suggest related but distinct use cases, but no guidance is given.

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