cancel_all_orders

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

With no annotations, the description carries full burden. It states the action and scope but omits details about side effects, irreversibility, permissions, or any confirmation/return behavior. For a destructive bulk operation, 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?

The description is a single, front-loaded sentence of about 10 words that directly states the action and optional filter. It is concise with zero wasted words, earning high marks for efficiency.

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 tool is simple with one optional parameter and no output schema or annotations. The description adequately covers the core function and parameter meaning, but it lacks any mention of return values, safety warnings, or why one might prefer this over 'cancel_order'. It is minimally viable but not rich in 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 schema provides only a regex pattern for the optional 'symbol' parameter with no description. The description adds meaningful context by explaining that the symbol is optional and filters which open orders are cancelled, compensating for the 0% schema description coverage.

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 verb 'Cancel' and resource 'all open orders', with an optional symbol filter. It distinguishes from the sibling 'cancel_order' by mentioning 'all', but does not explicitly contrast the two.

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?

No guidance is provided on when to use this tool versus the sibling 'cancel_order' or other alternatives. There is no mention of prerequisites, exclusions, or scenarios where this bulk cancellation might be inappropriate.

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