wsAmendOrder

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

With no annotations, the description carries full burden. It discloses that the tool places real orders, the response is only an acknowledgment, and that external verification (subscribeOrder or REST) is needed. It does not mention idempotency, failure modes, or whether modifications are atomic, leaving some gaps.

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 four sentences, the first presenting the purpose and the second a bold warning. It is front-loaded with key information, though it could be structured more formally with bullet points or sections.

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 (16 parameters, 2 required), no output schema, and high schema coverage, the description adequately covers the tool's operation and verification needs. It lacks error handling details or common constraints, but is largely sufficient.

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?

The input schema covers all 16 parameters with descriptions, achieving 100% coverage. The description adds minimal value beyond the schema, only reiterating that symbol, side, quantity, and price need user confirmation. Baseline score of 3 applies.

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 action (amend/modify), the resource (existing unfilled or partially filled order), and the context (via WebSocket on Bybit V5 unified account). It effectively distinguishes this tool from its siblings like createOrder and cancelOrder.

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 includes an important warning to confirm order details with the user before calling, but it does not explicitly state when to use this tool versus alternatives like the non-WebSocket amendOrder or when not to use it. It mentions subscribeOrder for verification but lacks comparative guidance.

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