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

Annotations already cover readOnlyHint, idempotentHint, and non-destructiveness. The description adds the precondition that the checkout must have been started by create_checkout, but does not disclose response contents or error behavior, which is acceptable given the strong annotation coverage.

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 communicates both the action and the required precondition with no filler. Every word serves a purpose.

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 simple read operation with one obvious identifier parameter and rich annotations, the description is sufficiently complete. It could mention the return shape, but the title already indicates status and no output schema is present.

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?

With only one parameter, checkout_id, the schema name is self-explanatory and the description confirms it identifies the checkout to read. However, schema description coverage is 0%, and the description itself adds no parameter-level detail, so it only earns average credit.

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 action ('Read'), a resource ('checkout'), and explicitly ties the tool to create_checkout, distinguishing it from the creating sibling. The title reinforces that it reads checkout status.

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?

The description clearly implies the tool is used after create_checkout has started a checkout. It doesn't explicitly name alternatives or exclusions, but the relationship to its creator sibling provides sufficient context for appropriate selection.

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