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

Annotations already indicate a safe, read-only, idempotent operation. The description adds valuable behavior beyond that: the pagination contract, the fact that results include source URL/format/locators, the caveat that publication.text is not assumed complete, and the collective-source interpretation. No contradiction with annotations.

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?

The description is compact and front-loads the main action in the first sentence. The later sentences about completeness and collective source are dense but informative; they could be more concrete, yet they do not waste the reader's time.

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 tool with no output schema, the description gives enough orientation: what is read, pagination behavior, and what the response includes. It does not document input parameters or exact response shape, but the schema's types/defaults plus the description's trail are sufficient for correct invocation.

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%, so the description needed to compensate for the three parameters. It only indirectly references pagination via 'nextOffset' and never explains publicationId, offset, or limit semantics. The ordered-sections phrase hints at offset usage, but the parameter meanings are largely left to the agent's inference.

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 states a specific verb and resource: 'Read the downloadable EPUB/PDF text in ordered sections.' It clearly differentiates this from siblings like search_publication_text by framing it as reading full text in ordered sections, and clarifies the scope with 'not necessarily one contained work.'

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 gives an explicit usage instruction: 'Continue using nextOffset until null,' which tells the agent how to paginate through the complete text. It does not explicitly name alternatives or when-not-to-use cases, but the reading-oriented context makes the tool's role clear relative to search siblings.

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