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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description's real contribution is the status vocabulary (waiting for payment, paid, ready to collect, collected, expired), which helps an agent interpret results in the absence of an output schema. It says nothing about not-found orders, invalid IDs, or error behavior, which matters for an open-world lookup.

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?

It is short and free of padding, but it is a bare fragment with no leading verb, so the core action is not front-loaded. A single added clause such as 'Returns the status of an order' would fix both structure and purpose at almost no length cost.

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?

With no output schema, the description carries the burden of explaining what comes back; it partially does so via the state list but never frames it as a return value. For a read-only lookup taking an order_id, it should at minimum state the input's meaning and the not-found case.

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 single required order_id parameter is undocumented in both schema and description. The description never mentions what an order_id is, where it comes from, or its format, so it fails to compensate for the coverage gap.

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 enumerates the possible order states but never states the verb or that it returns a status for a given order_id – it reads as a sentence fragment. An agent can infer a status lookup from the name and title, but the text itself never says what it does. It also does nothing to distinguish it from pay_order or get_pickup_pass, which touch the same order lifecycle.

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 when-to-use guidance, no preconditions, and no mention of the siblings (pay_order, create_pickup_order, get_pickup_pass) that an agent would need to choose between. The state list hints at polling use cases but never says so explicitly.

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