Get Order Status

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

Annotations already provide readOnlyHint=true and idempotentHint=true, so the description's read-only nature is redundant. The phrase 'latest status' adds a minor nuance about recency but does not disclose any additional behavioral traits such as caching, staleness, or failure modes. The description aligns with annotations, so no contradiction.

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 concise sentence that front-loads the verb and resource. No wasted words, and it is appropriately sized for a simple lookup 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?

The tool is simple but the single parameter is completely undocumented in both schema and description, leaving a significant gap in how to call it. While an output schema exists, the input side is lacking. Additionally, no guidance on prerequisites or differentiation from similar tools is given, making the description insufficient for an agent to reliably use it.

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% and the description merely repeats the parameter name 'order id' without adding any format, source, or validation details. Since the schema provides no description and the tool description does not compensate, an agent has no guidance on how to construct a valid order_id.

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') and resource ('latest status for a single order id'), which is specific and differentiates from siblings like list_open_orders (multiple orders) and get_order_set_status (order sets). The verb and resource are unambiguous.

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 usage is implied: it is for a single order id. However, there is no explicit guidance on when to use this tool versus alternatives like get_order_set_status or list_open_orders, and no exclusion criteria are given. An agent might still be uncertain about edge cases (e.g., order sets).

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