get-order-by-id

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

With no annotations, the description carries the full burden of behavioral disclosure. It does share what the response includes (line items, shipping address, totals), which is useful, but it does not mention behavior on missing/invalid order IDs, authorization requirements, or any rate limits. It is adequate but not thorough.

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, front-loaded sentence with no filler. Every word adds value: the action is first, the resource is bounded, and the return details are listed succinctly.

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 one-parameter read operation, the description plus schema supply what an agent needs: how to identify the order and what to expect in the response. It could be more complete by explicitly differentiating from get-orders, but this is a minor gap given the clarity of 'a single order' and the orderId parameter.

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 schema covers the only parameter, orderId, with a description that includes accepted formats. Since schema description coverage is 100%, the baseline is 3 and the description adds no additional parameter-level meaning beyond what the schema already provides.

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 action ('Get full details') and the resource ('a single order'), and specifies what is included (line items, shipping address, totals). This distinguishes it from sibling tools like get-orders, which lists multiple orders, and get-product-by-id, which targets a different resource.

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?

Usage context is implied by the phrase 'a single order' and the required orderId parameter, making it evident this tool is for fetching one specific order. However, there is no explicit guidance about when to use this instead of get-orders or any other alternative, leaving some inference to the agent.

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