BinanceConvertCancelLimitOrder

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

With no annotations provided, the description carries the full burden. It clearly states the action (canceling an order) and that it returns status, but it does not disclose details such as irreversibility, potential errors (e.g., order not found), or whether partial fills can be canceled. The mention of 'previously placed' gives some context, but the behavioral profile is minimal.

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 that clearly states the action and return value. It is front-loaded with the verb and resource, contains no redundant words, and is immediately understandable.

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 cancel operation with two well-documented parameters and no output schema, the description provides sufficient context. It states what is canceled and what is returned, though it could further clarify prerequisites (e.g., order must be in a cancellable state) or error handling, but these are not critical for basic invocation.

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 schema provides 100% coverage for both parameters: orderId is described as 'The orderId from placeOrder API' and recvWindow as 'Time window for request validity'. The description adds no further meaning beyond the schema, satisfying the baseline for high coverage but not exceeding it.

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 states a specific action ('Cancels'), a specific resource ('previously placed limit order'), and the method ('using the orderId'). It also mentions the return value ('cancellation status along with the orderId'). This clearly differentiates it from sibling cancel tools like BinanceDeleteOrder, which targets spot orders, while this targets Binance Convert limit 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 it is used for limit orders placed via Binance Convert, but it does not explicitly state when to use this tool versus alternatives like BinanceDeleteOrder or BinanceSpotCancelOpenTWAPOrder. No exclusions or alternative tools are mentioned, leaving the agent to infer the appropriate context from the tool name and description.

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