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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. However, the description adds nothing beyond that: it never mentions pagination (limit/cursor), the wait_seconds polling behavior, or that 'kind' selects a sub-resource — all of which materially affect how the call behaves.

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?

One short front-loaded sentence with zero filler, which is good, but the brevity comes at the cost of substance rather than from economy — it is under-specified rather than tight.

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 7 parameters, an enum selector, no output schema, and no parameter descriptions, the definition is far too thin for an agent to call this correctly. It should at minimum explain the kind/cursor/product_handle interaction and what a 'revision' is.

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% across 7 parameters, so the description must carry the load and does not. Nothing explains what 'kind' enum values mean, why 'product_handle' exists alongside 'kind', what 'build_id' identifies, or how 'wait_seconds' affects the read.

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 ('Read') and a specific resource ('structured commerce draft and revision'), which distinguishes it from commerce_draft_apply (a write) and hints at the draft-vs-live split against commerce_get. It stops short of naming any sibling explicitly, so an agent must infer the boundary from naming convention alone.

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?

There is no statement of when to use this versus commerce_get, commerce_draft_apply, builds_get, or builds_open, and no prerequisites or exclusions. The agent is left to guess from the tool name whether this reads a draft, a build revision, or both.

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