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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior. The description adds genuinely new information beyond them: the returned editions are immutable snapshots and include policy revisions. It does not describe pagination, ordering, or how many editions come back, but the annotations carry most of the safety profile.

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 dense sentence with the verb and scope front-loaded, and no filler. It is arguably over-terse given the undocumented parameter, but nothing in the sentence is wasted.

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?

An output schema exists, so return-value explanation is unnecessary, and annotations are rich. However, with a required parameter at 0% schema coverage, the description should explain what bookId is; that omission leaves a real gap for a tool whose only input is that parameter.

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% for the single required bookId parameter, which has only pattern and length constraints, with no textual explanation. The description never mentions bookId at all, so an agent cannot tell from the description whether it takes an internal ID, a slug, or a name. This is the main compensating gap the description was needed for.

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 (handbook editions) and qualifies the scope as 'immutable published', with the additional detail that policy revisions are included. This clearly separates it from generic getters like get_book, though it never names a sibling. It is clear but lacks explicit differentiation from list_document_versions or list_books.

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 description provides no guidance on when to call this versus alternatives such as get_book, list_books, or list_document_versions. The words 'published' and 'immutable' faintly imply that drafts are excluded, but no scene, prerequisite, or exclusion is ever stated.

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