deliveries_retrieve__get_deliveries_by_id

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

Annotations already declare readOnlyHint=true, so no safety surprise. The description adds error conditions (ValueError on invalid input), the XOR constraint, and MCP throttling limit (10/60s) with caching advice. This adds useful behavioral context beyond 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 compact, with main purpose first, then error conditions, ID sources, and throttling. It's well-structured and front-loaded, with no fluff.

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 read-only retrieval with a nested request object, the description covers the key constraints (XOR, max 200, error), ID sourcing, and rate limiting. Optional parameters are documented in schema, and no output schema exists, so completeness is adequate.

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 has detailed descriptions for parameters (orderIds, posOrderIds, etc.), but the description adds the XOR constraint, max 200, and where to get IDs. However, it doesn't cover all parameters (returnLockedByUser, returnExternalDataKeys) and relies on schema for those. Since schema coverage is low per context signal, the description only partially compensates.

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 it retrieves orders by ID, with the XOR constraint and maximum 200. It doesn't explicitly differentiate from the sibling get_delivery_by_id (singular), but the plural and list usage make it distinct. The purpose is clear enough.

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?

It provides where to get IDs (from other tools), and mentions throttling/caching, but does not explicitly state when to use this vs alternatives like search_deliveries or get_delivery_by_id. The guidance is implied but not explicit.

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