fetch_order

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

No annotations provided; description only says 'fetch,' implying read-only. No disclosure of side effects, authorization requirements, rate limits, or error conditions. The bare description does not compensate for the lack of 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?

A single, clear sentence with no wasted words. Conciseness is high, though adding a brief note about parameter validation could improve without sacrificing brevity.

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 tool with one parameter and no output schema, the description is minimally adequate. However, it lacks details like return format or pagination, which could be useful given the presence of sibling tools like 'fetch_all_orders' that likely differ in output structure.

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 coverage is 0% and description adds no meaning beyond the schema. The parameter 'order_id' is an integer but its format, source, or validation rules are not explained. The description does not help the agent understand how to populate this parameter correctly.

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?

Description clearly states 'Fetch a specific order by ID,' which is a specific verb+resource combination. It distinguishes from sibling tools like 'fetch_all_orders' (all vs specific) and 'place_*_order' (placement vs retrieval).

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?

No explicit guidance on when to use this tool versus alternatives like 'fetch_all_orders' or 'place_order' tools. The description implies context (when you have a specific order ID) but does not state exclusions or alternative conditions.

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