BinanceOpenOrderList

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

No annotations are provided, so the description carries the full disclosure burden. It only states 'Query open OCO orders for a specific account or symbol' but does not disclose whether symbol is optional, how pagination works, what the response contains, or whether this is strictly a read-only operation. The mention of 'specific account' is ambiguous given the schema only exposes a symbol parameter.

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 is front-loaded with the action and resource, containing zero wasted words. It is appropriately sized for the tool's simplicity.

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?

Despite low complexity (one optional parameter), the description omits crucial context: whether symbol is required, what the response looks like (no output schema), and how this relates to the authenticated account. It also lacks usage guidance and behavioral transparency, leaving the agent with incomplete information for correct invocation and interpretation.

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 already includes a clear example. The description adds no additional parameter-level meaning beyond what the schema provides, so the baseline 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 uses a specific verb ('Query') and resource ('open OCO orders'), clearly distinguishing it from the sibling BinanceGetOpenOrders which likely handles regular open orders. However, it does not explicitly name alternatives or explain the OCO distinction, so it is clear but lacks explicit sibling differentiation.

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 usage for OCO-specific open order queries via the keyword 'OCO', but it provides no explicit when-to-use instructions, exclusions, or references to sibling tools. Users must infer when to choose this over BinanceGetOpenOrders or BinanceOrderOco.

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