get_order

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

With no annotations, the description carries the disclosure burden. The verb 'Get' signals a non-mutating read and the description clearly states what is returned, but it does not mention auth requirements, behavior for invalid or missing ids, or explicit side-effect guarantees.

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 well-structured sentence with the main action front-loaded, followed by a compact comma-separated list of returned fields. It is slightly long but every clause adds specific information.

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 simple read-by-id tool with one documented parameter and no output schema, the description gives a thorough inventory of return content and identifies the source of the id. It lacks a pointer to get_order_pipeline for pipeline-specific details, but the core information needed to call it correctly is present.

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 description coverage is 100%, and the single parameter is already documented as the order id from list_orders with minLength 1. The tool description adds only 'by its id,' which does not materially extend the schema's parameter documentation.

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 leads with a specific verb and resource ('Get one order's full details by its id') and enumerates the exact fields returned, including items, money column, discount code, PO number, address, and statuses. It is clearly distinct from list_orders, though it does not explicitly differentiate itself from the sibling get_order_pipeline.

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?

There is no explicit when-to-use or alternative-routing guidance. The parameter description 'The order's id (from list_orders)' implies this tool is used after listing orders, which provides minimal context, but no exclusions or comparison to the related get_order_pipeline sibling are given.

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