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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, so the description does not need to restate those. It adds useful response-field context (language, version title, license, source) but no further behavioral caveats like pagination or completeness guarantees.

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?

Two compact sentences, front-loaded with purpose and followed by the essential usage pointer. No filler or redundant restatement of the schema.

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 read-only listing tool, the description gives the scope, return fields, and the next step. It is nearly complete, though it could strengthen the sibling distinction and clarify the effect of omitting the optional language filter.

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 the parameters 'book' and 'language' are already documented. The description adds only an indirect semantic note about version_title being consumed by get_text, which is helpful but not necessary for understanding either parameter.

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 description opens with a specific verb and resource: 'List every available edition and translation of a book', and names the returned fields. It is clear, but it does not explicitly distinguish itself from the similar sibling 'list_translations'.

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?

It clearly points to the follow-up tool: 'Use a version_title with get_text to read a specific translation', which implies the main use case. However, it does not state when not to use this tool or how it compares with sibling 'list_translations'.

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