get_order

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

Despite no annotations, the description indicates it returns multiple types of data (sub-orders, customer info). However, it does not disclose whether the operation is read-only, requires specific authorization, or any rate limits. Since it is a 'get' operation, it is likely safe, but lack of explicit info keeps the score at 3.

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?

Single sentence of 18 words, front-loaded with the action and resource. No redundant phrases, every word adds value. Efficient and clear.

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 simple tool (1 parameter, no output schema, no nested objects), the description adequately covers the purpose and included data. It lacks context on authentication or error handling, but for a basic retrieval tool it is fairly complete.

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 one parameter 'id' described in the schema as 'The order/booking ID'. The description merely says 'by its ID', adding no new semantics beyond the schema. Baseline 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 uses 'Get a specific order/booking by its ID' with a clear verb and resource, distinguishing from the sibling 'list_orders' tool. It also mentions included data (sub-orders, customer info, related data), so purpose is clear and specific.

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 is provided on when to use this tool vs alternatives. For example, it does not mention that this is for retrieving a single order by ID, while list_orders should be used for multiple orders. No exclusions or recommendations.

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