wsBatchCancelOrders

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

With no annotations, the description carries the full burden. It discloses that the tool modifies real orders via WebSocket, that the response is only an acknowledgment, and recommends verification. It could mention failure cases for already-filled orders, but overall is transparent.

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 two sentences plus a warning, with the purpose front-loaded. Every sentence adds necessary context without unnecessary verbosity.

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?

The description covers the core purpose and usage caveats, including verification steps. For a 2-parameter tool without output schema, it is reasonably complete, though it could mention error handling for partially successful cancels.

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 baseline is 3. The description adds minimal value beyond schema descriptions; it reiterates the need to confirm details but does not provide additional parameter nuance. The max limits per market type are already in schema (maxItems:20).

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 batches cancel operations for unfilled/partially filled orders via WebSocket on Bybit V5. The verb 'cancel' and resource 'orders' are specific, and the 'WebSocket' differentiates from REST-based siblings like batchCancelOrders.

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 advises confirming order details with the user before use and notes that the response is an acknowledgment, directing users to verify order status via subscribeOrder or REST. It provides clear context but does not explicitly compare to alternatives or state when not to use.

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