mb_cancel_all_orders

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It explicitly warns 'DANGEROUS', notes that multiple orders are cancelled at once, requires confirmation, and specifies the two-step preview/execute pattern. This effectively conveys the destructive nature and necessary safeguards.

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: three sentences with no filler. It front-loads the core purpose, then adds a danger warning, then gives a clear usage instruction. Every sentence contributes distinct value, making it well-structured and easy to parse quickly.

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 tool's complexity as a dangerous bulk operation, the description covers purpose, danger, and the exact confirmation workflow. It lacks an output schema, but the description does not need to explain return values since none are provided. It is sufficiently complete for an agent to select and invoke the tool correctly.

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 input schema already provides descriptions for all three parameters (100% coverage), establishing a baseline of 3. The description adds meaningful context by explaining how to use the confirm parameter ('Call with confirm=false first to preview, then confirm=true to execute'), and by mentioning the optional symbol filter, which aligns with and reinforces the schema descriptions.

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 tool cancels ALL open orders, with an optional symbol filter. It uses a specific verb ('Cancel') and resource ('ALL open orders'), and the scope is distinct from the sibling tool mb_cancel_order, which cancels a single 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 provides clear context for when to use the tool: to cancel all open orders, possibly filtered by symbol. It also outlines a preview-then-execute workflow with confirm=false and confirm=true. However, it does not explicitly contrast with mb_cancel_order or list exclusions, so it falls short of a full 5.

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