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

Annotations already declare readOnly=false, idempotent=false, destructive=false, openWorld=false, so the safety profile is covered. The word 'Replace' usefully signals overwrite semantics rather than a merge, but nothing is said about whether omitted fields are cleared, whether the session must be in a particular state, or what auth is needed.

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?

A single front-loaded sentence with no filler and the mutating field names early. However, at this length it is arguably under-specified rather than truly concise for a tool with a nested, undocumented schema.

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, but with 0% parameter coverage, nested objects, and no usage or state guidance, an agent lacks what it needs to call this correctly. 'UCP' is never expanded or contextualized.

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 three parameters (id, meta, nested checkout) are entirely undocumented. The description names line_items and buyer, which appear to be fields nested inside the checkout object, but it says nothing about 'id' or the mysterious 'meta' object, so it only partially compensates 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?

States a specific verb ('Replace') and resource ('line_items and/or buyer on a UCP checkout session'), so an agent knows exactly what is mutated. It is distinguishable from create_checkout/complete_checkout/cancel_checkout by the word 'Replace', but it never names or contrasts those siblings explicitly.

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?

No when-to-use guidance, no prerequisites, and no routing to alternatives such as get_checkout or complete_checkout. The agent must infer from the name alone when this step belongs in the checkout flow.

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