get_order_details

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

The annotation openWorldHint=true indicates the tool may return results influenced by external state. The description is consistent with that, but adds no additional behavioral context such as error handling, data freshness, or side effects. It does not contradict the annotation.

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, focused sentence that front-loads the action and purpose. No wasted words or redundant detail.

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 single-parameter read operation, the description is sufficient when combined with the schema. However, it does not specify what 'detailed information' includes or any error behavior, which could be helpful given no output schema exists.

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?

The schema already covers the single parameter 'orderid' with a clear description. The tool description merely restates 'by its order ID' without adding format, validation, or example. Since schema coverage is 100%, the description adds minimal value.

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 action (get), the resource (specific order), and the identifier (order ID). This distinguishes it from sibling tools like get_order_book, which list orders, by focusing on a single order lookup.

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 implies the tool is for single-order lookup when you have an order ID, but it does not explicitly contrast with list endpoints like get_order_book or mention any prerequisites. Usage context is implied rather than clearly stated with exclusions.

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