orders_get_order

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

With no annotations, the description must carry the transparency burden. The verb 'Retrieve' and the listed response fields clearly indicate a read-only operation, which is good. However, it does not disclose potential errors (e.g., order not found), permission requirements, or any side effects, leaving some behavioral aspects unaddressed.

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 sentence, front-loaded with the main action and resource. It conveys all necessary information without redundancy or 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?

The tool is simple (1 parameter, no output schema), and the description lists the key data components returned (line items, totals, status, shipping), which is helpful. It does not mention error handling or authentication, but for a straightforward retrieval tool, this is reasonably complete.

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 one parameter, order_id, with a clear description 'Unique identifier of the order to retrieve.' The description reiterates 'by its order ID' but adds no new semantics beyond the schema. With 100% schema coverage and a simple parameter, a 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 clearly states the verb 'Retrieve' and the specific resource 'full details of a single customer order by its order ID'. It lists the included fields (line items, totals, status, shipping) and distinguishes itself from siblings like 'orders_list_orders' or 'orders_search_orders' by emphasizing 'single 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 this tool: when you need full details for a specific order ID. It does not explicitly name alternative tools like 'orders_search_orders' for finding orders, but the singular 'single customer order' provides clear context. Lacks an explicit exclusion statement.

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