order_detail

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully flags the login requirement, but says nothing about read-only nature, what happens if the order_id is missing or belongs to another account, or how the 'full' flag alters the response.

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?

Two short sentences, front-loaded with the resource return and followed by the access constraint. No wasted words, though the terseness comes at the cost of substance rather than being paired with it.

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?

An output schema exists, so return-value documentation is not required, and the login requirement is disclosed. However, with zero schema coverage and no annotations, the undefined 'full' parameter and unqualified order_id format are meaningful gaps for a tool whose behavior hinges on them.

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 0%, so the description must compensate for both parameters and does not. The meaning of the optional 'full' boolean is completely unexplained, and the expected format of 'order_id' is left to guesswork; only the vague implication that line items are included hints at what 'full' might control.

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?

States a specific resource and scope: 'A single order with its line items.' The word 'single' implicitly contrasts with the list-returning my_orders sibling, but the description never names that sibling, so differentiation is left to inference.

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?

'Requires login' is a prerequisite, not usage guidance. There is no statement about when to reach for this over my_orders, last_order, or order_invoice, and no exclusions or error conditions are given.

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