batch_amend_order

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

No annotations are provided, so the description must fully disclose behavior. It states the tool amends multiple orders with limits but lacks details on partial failures, atomicity, error handling, or response structure. This is insufficient for a batch mutation 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 extremely concise (three sentences) with front-loaded action and no wasted words. The Args block is efficiently structured.

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 absence of annotations and output schema, the description covers basic functionality and limits but lacks details on error handling, idempotency, and partial success. It is adequate but not fully complete for a batch 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?

Schema coverage is 0%, so the description compensates by explaining the 'category' parameter with product types and 'orders' as a list requiring specific fields (symbol, orderId/orderLinkId) and optional ones. This adds meaning beyond the empty 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 amends multiple orders in a single request, with specific limits for derivatives and spot. It uses specific verbs and resource ('Amend multiple orders') and distinguishes from sibling tools like 'amend_order' (single) and other batch tools.

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 provides usage limits (max 20 for derivatives, 10 for spot) and implies batch use vs. single amendments. However, it does not explicitly state when not to use this tool or mention alternatives like multiple single-order amendments.

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