cancel_pending_order

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

No annotations are present, so the description carries the full burden. It says 'Delete,' implying a destructive mutation, but does not disclose reversibility, required permissions, behavior if the order has already filled, or what is returned. For a mutation tool with zero structured behavioral coverage, this is a significant gap.

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?

A single, front-loaded sentence with no wasted words. It is appropriately sized for the amount of information it attempts to convey.

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 no annotations, no output schema, and 0% parameter coverage, the description is incomplete: it omits parameter semantics, error conditions, and comparison to sibling tools. The core action is stated, but an agent lacks enough context to invoke it confidently in edge cases.

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 description coverage is 0% for the single required `ticket` parameter, and the description never explains what the ticket is, its format, or how to obtain it. It only refers to 'a pending order' generically, adding no meaning beyond the schema's property name.

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 names a specific verb ('Delete') and resource ('a pending order') and adds the temporal condition 'before it fills,' so an agent can tell it targets unfilled orders. It does not, however, distinguish itself from siblings like modify_pending_order or close_position; that sibling differentiation is absent.

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?

Usage is implied: cancel a pending order when you don't want it to execute. There is no explicit when-to-use/when-not guidance, no named alternatives, and no prerequisites (e.g., needing an order ticket). Score 3 for implied usage only.

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