BinanceDeleteOpenOrders

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

With no annotations, the description must carry the full burden. It discloses the destructive action and exact scope ('all open orders'), but does not mention irreversibility, permissions, rate limits, or return format. The verb 'Cancel' implies mutation, and the description clarifies exactly what is affected.

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?

One concise sentence that is action-first and free of redundant wording. It conveys the tool's purpose and scope with minimal length.

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 simple one-parameter cancel-all tool, the description sufficiently explains the core operation. However, it does not specify the response format or mention edge cases (e.g., when there are no open orders), but these are minor gaps given the tool's simplicity.

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%, and the schema already provides a clear description of the 'symbol' parameter with an example ('BTCUSDT'). The description's 'specific symbol' adds no extra semantic value beyond what the schema already provides.

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 a specific verb ('Cancel') and resource ('all open orders on Binance') with a clear scope ('for a specific symbol'). It distinguishes from siblings like BinanceDeleteOrder (single order) and BinanceGetOpenOrders (read-only).

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 intended use is implied: use this tool to cancel all open orders for a symbol. However, it does not explicitly mention when to prefer this over BinanceDeleteOrder or other alternatives, and it lacks exclusions or when-not-to-use guidance.

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