batch_orders

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

Without annotations, the description only mentions the operation and constraints. It does not disclose error handling, partial success behavior, rate limits, or other side effects, leaving the agent underinformed for a write operation.

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 single, compact sentence with no wasted words, front-loading the core purpose and constraints.

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?

The description lacks details on return values, error scenarios, and usage context relative to siblings. For a batch tool with no output schema or annotations, more information is needed.

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 100% for the single parameter. The description adds the critical constraint that all orders must share instId and marginMode, which is not captured in the schema description.

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 places multiple orders at once, with specific constraints (up to 20, same instId and marginMode), distinguishing it from single-order 'place_order'.

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 implies when to use (batching with shared attributes) but does not explicitly mention when not to use or alternative tools like 'place_order' for single orders.

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