BinanceDeleteOrder

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it merely restates the tool's purpose ('Cancel an active order') without detailing irreversible effects, required permissions, or behavior if the order is no longer active. This is minimal and offers little beyond the tool's name.

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, concise sentence that is front-loaded with the core action. Every word earns its place, and it is appropriately sized for a simple cancellation tool.

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 no output schema and no annotations, the description is somewhat under-specified for a mutation tool. It does not mention required permissions, error scenarios, or that orderId and origClientOrderId are alternative identifiers. However, the parameter schema is well-documented, partially compensating for the lack of behavioral 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?

Schema coverage is 100% with each parameter having a clear description. The tool description adds minimal semantic value, only reinforcing that the symbol identifies the trading pair. It does not clarify the optionality or relationship between orderId and origClientOrderId, but the schema already describes these adequately.

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), the resource (an active order on Binance), and the scope (specific trading pair). It distinguishes from sibling tools like BinanceDeleteOpenOrders, which cancels multiple open orders, and BinanceCancelAlgoOrder, which targets algo orders.

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 implies use for canceling a single active order on a specific trading pair, but provides no explicit guidance on when to use it vs alternatives like BinanceDeleteOpenOrders, nor any prerequisites or exclusions. Usage context is implied but not directly stated.

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