read_book

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

With no annotations, the description carries the full burden and does well: it discloses on-demand conversion by calibre, cache reuse across calls, and explicitly states the library is never modified. It also mentions the return structure (chunk, next_offset, total_chars). This is strong behavioral context, though it omits potential error conditions or performance implications of first-time conversion.

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 efficiently structured: a one-sentence purpose, a short behavioral note, and a bullet-point Args list. Every sentence earns its place, and the most important information is front-loaded. No filler or redundant restatement of the tool name.

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?

Given the low complexity (one required integer parameter and two optional integers) and the existence of an output schema, the description is complete. It covers purpose, conversion/caching behavior, parameter semantics, and the key return fields needed for paging. There is nothing an agent needs to invoke and page through the book that is missing.

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 fully compensate, and it does. The Args block explains book_id ('find it with search_books'), offset as a character offset with the 0 meaning, and limit with range (1-40000) and default (12000). This adds substantive meaning beyond the raw schema properties.

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: 'Read a page of a book's plain text, converted on demand by calibre.' This clearly identifies what the tool does. It does not explicitly contrast with siblings like search_in_book, but the verb 'read' plus 'plain text' strongly implies the distinction, so it falls just short of a 5.

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 implies when to use the tool: whenever you need to read a book's text content, with paging via offset/limit. It also tells the user to find book_id via search_books. However, it does not explicitly state when not to use it or mention alternatives such as search_in_book for searching within the text, so the guidance is present but not thorough.

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