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

Read-only, idempotent, non-destructive, and closed-world behavior are already declared in annotations, so the description does not need to restate them. It adds useful workflow context about consent and order_url recovery, but leaves return shape, auth, and retrieval behavior unstated; with annotations covering safety, that is a moderate gap.

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, with the workflow condition front-loaded and no obvious filler. The wording is dense and slightly ambiguous, but it stays short and task-focused.

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 output schema, the description gives the workflow trigger and the states being checked, but omits the input's meaning and the returned data shape. It suggests the recovery use case but is not enough to call it confidently without inspecting schema or other tools.

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?

The sole required parameter preparation_id has 0% schema description coverage and is not mentioned in the description, so the agent gets no explanation of what ID to supply or where to obtain it. The parameter name and min/max constraints are the only guidance.

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 explains that this belongs to an optional consent workflow and checks browser consent plus an existing order_url, but it never plainly states that it retrieves a checkout preparation by ID or what the result represents. The verb 'check' and the workflow context help separate it from duplicating checkout, but not clearly from siblings like get_order or prepare_checkout.

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?

It gives a clear timing condition ('after return/uncertainty') and an explicit exclusion ('instead of duplicating checkout'), which helps an agent choose it in the recovery path. It does not name a sibling alternative or state prerequisites such as where preparation_id comes from.

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