batch_get_orders

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

No annotations are provided, so the description must carry the transparency burden. 'Get detailed information' accurately indicates a read operation, but it does not mention potential partial failures, the upper limit behavior beyond the schema's '1-1000' hint, or any other edge-case behavior. This is acceptable but leaves some ambiguity.

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 concise sentence that consists only of the essential purpose. It is front-loaded with the action and resource and contains no filler or redundant wording.

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 tool is a straightforward batch read operation with a fully described input schema and an output schema. The description clearly states the core behavior and batching intent. It is slightly sparse regarding failure handling or limits beyond what the schema provides, but the existing context is sufficient for simple selection.

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 has 100% coverage of both parameters, including a descriptive note that order_ids is a list of IDs from 1 to 1000. The description does not add semantic details beyond what the schema already provides, so the baseline of 3 is appropriate.

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 'Get detailed information for multiple orders at once' uses a specific action verb ('Get') and resource ('orders'), and clearly distinguishes this batch tool from the sibling get_order by emphasizing the 'multiple...at once' batching capability.

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 phrase 'at once' provides clear context that this tool is for retrieving multiple orders in a single call, implying it should be used instead of the single-order get_order when batching is needed. It does not explicitly name alternatives, but the batch context is clear enough.

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