get_order

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

Annotations already establish read-only safety. The description adds value by detailing the contents of the response (billing, shipping, line items, payment info) and the field-selection capability, providing more context than the annotation alone.

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?

Two concise sentences with a clear purpose statement followed by a practical tip. No redundant or filler content.

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 tool with two parameters, the description sufficiently explains what the tool returns and how to tailor it. It does not explain error cases or require exact output structure, but given the absence of an output schema, the listing of included details 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 description coverage is 100%, and the schema already explains both 'id' and 'fields' with defaults. The description's mention of 'fields param' is a minor reiteration, adding little semantic meaning beyond the structured schema.

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 'Get' with a specific resource 'single order' and lists the included content (billing, shipping, line items, payment info), which distinguishes it from list_orders and other order-related tools.

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 implies usage for retrieving full details of an order, and the 'Use fields param' tip gives practical guidance. However, it does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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