cancel_all_orders

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

Annotations already indicate destructiveHint: true; the description adds 'HIGH risk - requires confirmation', providing clear behavioral context of mutability and safety confirmation. It explains that it cancels all open orders, which is essential. Could detail side effects like irreversible loss of pending orders.

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 concise at two sentences plus a minimal parameter list. Front-loaded with purpose and risk. Could be slightly more structured with bullet points, but it's efficient and avoids 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?

An output schema exists, reducing need to describe return values. However, for a high-risk destructive tool, additional context about system-wide effects, partial cancellation behavior, and confirmation mechanism would be helpful. The description is adequate 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?

Schema descriptions are absent (0% coverage), so the description carries the burden. It lists parameters with brief meanings: category includes enum values 'spot, linear, inverse, option', and others are described as 'product type', 'symbol name', etc. This adds value over bare schema, though more detail on constraints (e.g., which params are required) would improve.

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 all open orders', specifying the action and scope. It distinguishes from sibling 'cancel_order' by targeting all orders, not just a single one. The HIGH risk warning adds context.

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 warns of HIGH risk and confirmation requirement, but does not explicitly state when to use vs. alternatives like 'cancel_order'. It lacks guidance on scenario selection or prerequisites.

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