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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description owes little on safety. However, it adds nothing about behavior, and notably leaves unresolved the tension between a read-only annotation and a `to` parameter enumerating state transitions, which is exactly the ambiguity an agent needs clarified.

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, but the brevity is under-specification rather than economy; a six-word fragment carries no actionable information and is not front-loaded toward any decision the agent must make.

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 three parameters, a state enum, no output schema, and no parameter descriptions anywhere in the structured data, this description is far too thin for the agent to invoke the tool correctly. Nothing compensates for the empty schema coverage.

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% across all three parameters (order, to, note), and the description supplies no semantics for any of them. The meaning of `to` — a target state transition versus a filter — is entirely undocumented, so an agent must guess.

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 "An order and its next step" is essentially a restatement/expansion of the tool name with no verb identifying what operation is performed (retrieve? advance? validate?). It hints at order lifecycle context but an agent cannot tell whether this reads status, computes the next allowed transition, or performs one.

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 indication of when to use this tool, no prerequisites, and no mention of alternatives among the many lifecycle-adjacent siblings (pay_status, ship_update, listing_get, order-related flows). The single fragment offers no routing value.

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