amendOrder

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

No annotations provided, so description carries full burden. It discloses that response is acknowledgment only, the order must be open, and updates can include price, qty, TP/SL, and orderIv for options. However, it does not reveal side effects, authentication needs, rate limits, or what happens on failure.

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 short, front-loads the main purpose, and uses bullet points effectively. Every sentence adds value with no redundancy.

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 16 parameters and no output schema, the description covers core behavior and constraints but is incomplete on parameter details and return value. It also lacks error handling context, which is important for a modification tool.

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?

With 0% schema description coverage, the description explains 9 out of 16 parameters (category, orderId, orderLinkId, price, qty, triggerPrice, takeProfit, stopLoss, orderIv) and gives usage tips for options and TradFi. But 7 parameters remain unexplained, including tpslMode, triggerBy, and limit prices.

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 verb 'modify' and resource 'existing open order', lists the updatable parameters (price, quantity, trigger price, TP/SL), and distinguishes from sibling tools like createOrder or 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?

Provides clear conditions for use: must provide orderId or orderLinkId, only unfilled/partially filled orders, and category hints for TradFi. Also acknowledges response is merely acknowledgment and advises confirmation via WebSocket. However, does not explicitly compare with batchAmendOrders.

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