cancel_all_pending_algo_orders

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

Without annotations, the description carries full burden for behavioral disclosure. It only states the action but does not clarify scope when symbol is omitted, side effects, cancellability, or any required permissions. The behavior of canceling across all symbols or only for a specified symbol is implied by the schema but not stated.

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 sentence with no extraneous words. It is efficiently structured and front-loaded with the core action. However, it may be too terse given the lack of additional context.

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?

For a tool with one simple optional parameter and no output schema, the description is minimally adequate. It states the basic function, but does not clarify behavior when parameter is omitted or how it differs from related sibling tools. A more complete description would include the scope effect of the optional symbol and references to alternatives.

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 coverage is 100% for the single parameter 'symbol', which is already described as optional with a clear purpose. The description adds no extra meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 action (cancel) and resource (all pending algo orders). It is specific enough to distinguish from tools like cancel_algo_order, though it does not explicitly differentiate from cancel_all_pending_orders. The verb+resource combination is direct and unambiguous.

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 no guidance on when to use this tool versus alternatives such as cancel_algo_order (for a single order) or cancel_all_pending_orders (for all order types). It does not mention any prerequisites, filters, or when-to-use/not-to-use conditions.

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