cancel_all

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

No annotations provided. Discloses dry_run=true default, but lacks details on auth requirements, rate limits, or reversibility.

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?

Two sentences, no wasted words. Information is front-loaded and immediately actionable.

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?

Adequate for a simple tool with 2 params and no output schema. Mentions default behavior and typical usage context. Could elaborate on requirement to set dry_run=false for actual cancellation.

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 covers symbol parameter description; dry_run lacks schema description. Description adds default value for dry_run, partially compensating.

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?

Describes canceling every open order with optional symbol filter. Clearly distinguishes from siblings like cancel_order and flatten_positions.

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?

Provides context as a 'panic stop' primitive used after set_kill_switch. Does not explicitly list when not to use, but implications are clear given siblings.

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