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

Annotations mark this as not read-only (readOnlyHint=false) despite the 'get_' name; the description reconciles that by disclosing it may 'continue safe payment reconciliation,' i.e. perform side effects. That is genuinely useful context beyond the annotations, though it never says what reconciliation actually mutates or how often it fires.

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 tight sentences with the primary action front-loaded and the completion rule second. No filler, though 'when appropriate' is loose phrasing that costs a little precision.

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 should describe what an 'authorized order state' actually returns, but it only names one terminal value ('fulfilled'). For a non-read-only, open-world tool touching payment flows, the behavioral surface is under-described.

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 100% (order_id UUID provenance, access_token secrecy/length all documented in the schema), so the baseline is 3. The description adds no parameter-level detail beyond what the schema already provides.

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 clear verb+resource ('Return the authorized order state') and defines what completion means ('status is fulfilled'). It does not explicitly contrast itself with siblings like check_payment or get_payment_requirements, and the 'continue safe payment reconciliation' clause blurs whether this is purely a status read.

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?

'Continue safe payment reconciliation when appropriate' implies a usage context but never defines the condition — 'when appropriate' is left to inference. The 'treat as complete only when fulfilled' line is interpretive guidance rather than a when-to-use-this-vs-alternatives rule.

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