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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety bar is pre-met; the description adds real value by stating what the record exposes (turn state, last checkout attempt, per-order charge status) and its reconciliation role. No auth, rate-limit, or pagination notes, but those are minor for a read-only call.

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 sentences, front-loaded with the verb and resource and then the use case; little waste. The long parenthetical of failure states is dense but each element is load-bearing, so it earns its space.

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?

An output schema exists, so return values need not be explained, and the description covers inputs, purpose, and the operational trigger well. The one real gap is the absence of any differentiation from get_purchase_turn, which an agent choosing between the two would want.

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?

Only one parameter with 100% schema description coverage, so the schema already documents `conversation_id` as the id from a purchase turn. The description adds no format, sourcing, or edge-case detail beyond that, making the baseline 3 correct.

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 specific verb+resource (read a purchase conversation's orders) and enumerates the payload: turn running state, last checkout attempt, and each order's charge status. It is clear what the tool returns, but it never names or distinguishes itself from the sibling get_purchase_turn, which an agent must disambiguate against.

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?

Gives concrete when-to-use guidance: to track an order, and to settle an unclear outcome before repeating a confirm, with the exact triggers (`in_progress`, `charge_status: unknown`, `failed` turn). It lacks any when-not or explicit alternative routing, so it stops short of a 5.

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