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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: that using an item elsewhere does not mutate the book, the page size of 100, and the API-key access requirement.

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?

Front-loaded with the core purpose, but the first two sentences restate the same idea ('Services and materials ... with their prices' vs 'Returns the services and materials ... with names and prices'), which is redundant for a short description.

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 read-only list tool with 100% schema coverage and no output schema, the description covers purpose, pagination, auth, and non-mutation, which is sufficient for correct invocation. Return-value details are not required given the schema-only surface.

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 100%, so all four parameters (kind, limit, query, cursor) are already documented. The description only loosely gestures at query ('Search by name') and limit ('Pages hold up to 100 items'), adding little beyond the schema, so baseline 3 applies.

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 (list) and resource (services and materials in your Price book with names and prices), and the scope is unambiguous. No sibling tool covers the Price book, so an agent can tell this read/list tool apart from the estimate/job creation siblings at a glance.

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?

Gives clear use context ('so a new estimate or job uses the prices you already set') and a search hint ('Search by name'), plus a prerequisite (Cotlet API key with access). It stops short of naming alternatives or explicit when-not conditions, so it is clear but not exhaustive.

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