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

No annotations are provided, so the description carries the full disclosure burden. It does add real value by naming the returned fields (band, capacity, hours note) and disclaiming that the result is not an offer, but it says nothing about permissions, error behavior for an invalid classId, or caching/staleness of price-book data.

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?

Three short, front-loaded sentences with no filler; the core identity of the resource comes first. It is efficient, though the clipped phrasing ('Same band, capacity, and hours note as the book page') leans on context the agent may not have.

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 single-parameter read with no output schema, the description supplies what matters: what is fetched, how it is keyed, what fields come back, and what it is not. Missing only failure behavior and any relation to the list sibling.

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 single classId parameter has 100% schema description coverage and an enum of eight valid values, so the schema already does the heavy lifting. The description's 'by id' adds only minimal framing beyond the schema-defined 'Price book class id.'

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-free but unambiguous retrieval: 'One class from the price book, by id.' The singular 'one class' implicitly contrasts with the sibling list_price_bands, and 'Not an offer' rules out a nearby concept. It stops short of naming the sibling explicitly, so it is clear but not maximally differentiated.

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 call this versus list_price_bands, desk_terms, or illustrate_financing. 'Not an offer' clarifies what the result is, not when the agent should prefer this tool, so usage must be inferred from the name and enum.

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