get_book_text

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

With no annotations provided, the description carries the behavioral burden. It discloses the read-only nature ('Read'), the server-side download-and-parse behavior on each call, and the 128 MiB cap refusal. It doesn't mention authentication requirements or error handling beyond the cap, leaving some gaps.

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?

Three tightly packed sentences, front-loaded with the core purpose and then escalating into operational detail. There is no filler and no repetition of schema defaults.

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 values don't need restating. The description covers the main calling modes, pagination, and the resource size cap, making it complete for a tool of this complexity.

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 must compensate, and it does: it defines chapter vs no-chapter behavior, offset continuation, and max_chars truncation. It doesn't explain book_id, but its role is self-evident from the name and the required flag in the schema.

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 phrase uses a specific verb ('Read') plus resource ('text of a book') and the qualifier 'one chapter at a time', which clearly separates it from sibling tools like get_book or list_books. The two operational modes (TOC vs chapter text) add further precision.

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 explains the two calling modes and the paging contract: without chapter returns the TOC, with chapter returns text cut to max_chars from offset, and next_offset continues for longer chapters. It doesn't explicitly name alternatives or state when not to use this tool, so it falls short of a 5.

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