batchAmendOrders

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

Despite no annotations, the description discloses key behaviors: mutation of orders, per-order status checking via retExtInfo.list[].code, that the response is only an acknowledgment and not confirmation (use WebSocket stream), and constraints on order state. This fully compensates for missing annotations.

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 a clear bullet list with an agent hint section, front-loaded with the main action. Each sentence adds value, though the TradFi hint could be condensed. Overall well-structured and concise.

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?

For a complex batch modification tool with no output schema, the description covers purpose, constraints, per-order status, and verification method. It addresses alternatives and use cases. Lacks some details on error handling or response structure beyond acknowledgment, but is sufficient for an agent to use correctly.

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 0%, so description must compensate. It explains that each item in the request array requires symbol and either orderId or orderLinkId, and mentions category values for TradFi. However, many fields in the request object (e.g., qty, price, triggerPrice) are not explained. The description adds some value but is not exhaustive for all parameters.

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 modifies multiple existing open orders in a single call, specifies the verb 'modify' and the resource 'multiple orders', and distinguishes from sibling tools like the single-order amendOrder via the agent hint.

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 guidelines include using this endpoint for multiple orders vs amendOrder for single orders, max order limits per request (20 for futures/options, 10 for spot), prerequisites like orderId/orderLinkId, and condition that only unfilled/partially filled orders can be amended. TradFi guidance for category usage is also provided.

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