get_order

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

Beyond the annotations (readOnlyHint, idempotentHint, openWorldHint), the description adds no behavioral context. It does not disclose return format, error behavior (e.g., 404 if order not found), or that it fetches by ID. Annotations cover safety, but the description is purely explicit without additional value.

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, concise sentence with no redundant words. It is front-loaded and appropriate for a simple get tool, but could include a bit more context (e.g., 'by ID') without significant bloat.

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 existing annotations, the description is minimally adequate. However, there is no output schema and the description does not mention that the tool returns an order object or that it uniquely identifies the order via order_id. This leaves some context gaps, though the schema helps.

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 100% with order_id described as 'the id of the order'. The description 'Fetch an order' adds no further meaning to the parameter, so it does not exceed the schema's baseline.

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 'Fetch an order' clearly states the action (fetch) and resource (order), making the tool's purpose understandable. However, it does not differentiate from sibling tools like get_order_pdf or list_orders, as it lacks specifics about fetching a single order by ID.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that this retrieves a single order by ID, nor does it contrast with list_orders or search_orders. No usage context or exclusions are given.

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