Get order

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

With no annotations, the description carries the behavioral burden. It states the scoping constraint ('belonging to the authenticated user') but does not disclose what happens if the order is not found, whether the operation is read-only, or any authorization requirements. The verb 'Retrieve' implies a safe read, providing basic transparency without detail.

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, direct sentence with no filler. The key information (action, resource, ownership) is front-loaded and every word earns its place. Ideal conciseness for a simple retrieval tool.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description conveys the essential intent but lacks guidance on use cases and error behavior. It is minimally viable but leaves the agent to guess about return format and failure modes.

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 order_id parameter is well-documented ('Order ID returned by place_order'). The tool description adds no additional parameter context beyond the schema, so a baseline of 3 is appropriate.

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 states a specific verb ('Retrieve') and resource ('one order'), and clarifies ownership ('belonging to the authenticated user'). It distinguishes from order_history by implying a single order fetch, though it does not explicitly mention lookup by ID. Clear enough for an agent to understand the core function.

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 guidance on when to use this tool versus alternatives like order_history or cancel_order. The description does not mention conditions such as needing an order_id from place_order, nor does it contrast with list operations. An agent must infer usage from the parameter schema alone.

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