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

With no annotations supplied, the description carries the full behavioral burden. It does disclose the domain of returned values (the six status states), which is real output context, but it says nothing about whether the call is a safe read, what happens when an order_id does not exist or is not visible to the caller, or whether the status is computed live versus cached.

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 short sentence with the resource front-loaded and the state list presented compactly after a colon; nothing is padding. Minor deduction for the fragmentary phrasing, which costs a beat of clarity without adding length.

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 tool with no annotations and no output schema, the enumeration of possible statuses substantially covers the return-value gap. It still leaves out failure behavior (unknown or unauthorized order_id) and does not state that the operation is non-mutating, which are the remaining things an agent would want before calling 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% for the single order_id parameter, so the description must compensate and it does not — it never mentions the identifier, its expected format, or whether it is a platform order ID versus a merchant reference. The parameter is largely self-explanatory from its name, which prevents this from being a 1.

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 identifies the resource (an order) and what is being retrieved (its current lifecycle stage), and enumerates the possible statuses, which none of the sibling names (create_order, list_orders, get_fix_brief) cover. It lacks an explicit verb — 'Where an order is' is a fragment rather than 'returns the status of' — but the intent is unambiguous to an agent.

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?

There is no statement of when to use this tool versus list_orders or get_fix_brief, and no prerequisites or exclusions. An agent can infer it is a per-order lookup from the required order_id, but that inference comes from the schema, not the description.

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