BinanceOrderOco

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Send a new OCO order.' It fails to explain what an OCO order does (one cancels the other), any side effects, order lifecycle, or constraints. No behavioral traits beyond the action are disclosed.

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, front-loaded sentence with no wasted words. It is appropriately concise for a tool that is otherwise well-documented through its schema.

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?

This is a complex order type with 11 parameters, no annotations, and no output schema. The description is far too minimal to provide complete context. It does not explain OCO semantics, how the limit and stop legs interact, or what the response contains, making it inadequate for an agent to fully understand the tool.

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 description coverage is 100%, so the baseline is 3. The description adds no parameter-level meaning beyond what the schema already provides. It does not clarify how parameters like stopLimitPrice or stopIcebergQty relate to OCO behavior, but the schema descriptions are sufficient for basic understanding.

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 tool sends a new OCO order on Binance, using a specific verb ('Send') and resource ('OCO order'). It distinguishes itself from sibling tools like BinanceNewOrder and BinanceDeleteOrder by naming the special order type.

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?

No guidance is provided about when to use this tool versus alternatives. It does not mention when an OCO order is appropriate, prerequisites, or that regular orders should go through BinanceNewOrder. The context of usage is entirely absent.

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