wsBatchAmendOrders

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

No annotations provided, so description carries burden. Discloses real order modification, WebSocket usage, and acknowledgment-only response. Does not fully cover limits or order types (e.g., conditional orders) but provides useful warnings.

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?

Two sentences plus an IMPORTANT note, all front-loaded with essential information. No redundancy or fluff.

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?

Covers main behavioral aspects: batch modification, WebSocket, acknowledgment, verification need. Missing mention of max batch size (in schema) and applicability to conditional orders, but overall sufficient given complexity.

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 baseline 3 applies. Description adds no extra meaning beyond schema; does not explain parameters further.

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?

Description clearly states the action (batch amend), resource (multiple existing unfilled or partially filled orders), and context (WebSocket request on Bybit V5 unified account). It distinguishes from siblings like 'amendOrder' and 'wsAmendOrder' by specifying batch operation and order state.

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?

Provides explicit user confirmation requirement before calling and clarifies that response is only an acknowledgment, with alternative verification methods. Lacks explicit when-not-to-use versus alternatives like batchCancelOrders, but context is clear enough.

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