wsBatchCreateOrders

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It warns that the tool places real orders and that the response is not a confirmation. It does not disclose potential issues like partial batch failures, execution order within the batch, or rate limits, which are important for a batch tool.

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 concise with two sentences and a warning paragraph. It front-loads the purpose and provides critical usage guidance without unnecessary detail. Every sentence adds value.

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?

Given the tool's complexity (array of 20+ fields per order, batch execution, no output schema), the description lacks information on batch behavior (atomicity, error handling, ordering), prerequisites (e.g., WebSocket connection), and the exact nature of 'modify' claims. It is incomplete for a tool that can have significant financial impact.

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% for both parameters, so the baseline is 3. The description does not add parameter-specific semantics beyond the schema; it only references confirming symbol, side, quantity, and price, which are already documented in the schema.

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's purpose: batch placing multiple orders via WebSocket on Bybit V5 unified account. It distinguishes from similar tools like wsCreateOrder (single order) and batchCreateOrders (REST) by specifying the WebSocket transport. The verb 'place' matches the tool name, though 'modifies' is slightly ambiguous for a create-only tool.

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 calling and notes that the response is only an acknowledgment, recommending subscribeOrder or REST endpoints for verification. However, it does not explicitly state when to use this tool vs its siblings (e.g., REST batchCreateOrders) or provide exclusions for unsupported order types.

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