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

Beyond the annotations it discloses two non-obvious behaviors: an unfilled entry being cancelled takes its own stop and take-profit with it, and the tool works while trading is halted. It does not cover permission requirements or partial-failure behavior, so it falls short of fully exhaustive, but it materially exceeds what destructiveHint/idempotentHint alone convey.

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?

Tight, front-loaded prose: the primary action and both modes come first, then side effects, then exclusions and the next step. No filler sentences and no restatement of the title.

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?

With an output schema, full parameter coverage and descriptive annotations, the description covers the remaining agent-facing gaps: destructive side effects on attached exits, availability during halts, and sibling routing. Only auth/scope expectations are unaddressed, a minor gap for a mutation 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 coverage is 100%, so the baseline is 3; the description adds the either/or relationship between order_id and all_waiting_entries and clarifies that the symbol-wide mode targets unfilled entries only. The remaining venue-default and length constraints are left to the schema, which 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?

States a specific verb and resource plus both operating modes: cancel one resting order by order_id, or every unfilled entry on a symbol via all_waiting_entries: true. It also names what it is not (close_position, tighten_stop_loss), so an agent can separate it from siblings without opening a schema.

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?

Explicit when-to-use (withdraw unfilled orders or a take-profit) and explicit when-not (not for closing positions; not for a held position's stop-loss, which stays until close and is instead tightened with tighten_stop_loss). It also names a concrete follow-up, get_my_open_orders.

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