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

readOnlyHint=true already declares the safe-read profile, so the bar is lower. The description adds genuine value beyond that by disclosing the cents unit for price/cost and the default-empty nested lists, but says nothing about pagination limits, auth requirements, or result size.

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 dense sentence that front-loads the action and returned fields, followed by a short API endpoint reference. Every clause carries meaning, though the field enumeration makes it slightly long.

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 no output schema, enumerating the returned fields and the optional nested expansions is exactly what the description should do, and all schema parameters are covered. It stops short of noting pagination or auth behavior for the API-backed call.

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 six parameters (q, page, page_size, expand, sort_by, sort_direction) are already documented in the schema. The description's only added parameter meaning is the cents unit for the monetary fields, which is marginal.

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 and resource ('List or search the price book's services') and enumerates the returned fields (name, task number, price/cost in cents, taxable and online-booking flags). No sibling tool covers the price book, so there is no ambiguity to resolve.

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 'List or search' phrasing plus the optional 'expand' clause implies when to use it (browse or query services, optionally with nested materials/labor rates), but there is no explicit when-not guidance or named alternative among the many list_* siblings.

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