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

Annotations already establish the read-only, idempotent, non-destructive profile, and the description goes well beyond them: it discloses the REST-shaped return, pagination totals and next/previous links, how to advance ('increment page to continue'), and that results are never silently truncated. Those are non-obvious behavioral traits an agent cannot infer from the annotations or schema.

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 verb and the browse/search distinction, then return and pagination details, then the sibling routing hint. Most sentences earn their place, but 'Includes publication-filtered relationships and public links' is vague filler that does not tell an agent anything actionable.

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, the description correctly carries the burden of explaining return shape (public REST representation, pagination totals, next/previous links) and continuation behavior. What is missing is only minor: sort and slug are left entirely to the schema, and ordering semantics are not mentioned.

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 coverage is 67%, and the description compensates for the gaps that matter most: the meaning of omitting q, the role of page in continuing pagination, and the per_page/size tradeoff. It adds little for sort, slug, and author_id, which the schema already documents, so it falls short of fully covering the remaining third.

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?

The opening sentence names a specific verb pair and resource ('List or search published books') and immediately separates the two modes via 'Omit q to browse all records.' It also explicitly names the sibling get_book as the choice for a known ID, so an agent can distinguish it from alternatives without opening any schema.

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 explicit when-to-use guidance: omit q to browse, supply q to search, and use get_book instead when the ID is already known. It also states a concrete operational remedy ('large pages may require a smaller per_page'), which is the kind of conditional direction agents need.

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