Get chapter text

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently reveals the output cap, default maxChars, and the offset/nextOffset paging mechanism, which are not evident from the schema. It doesn't cover edge cases like invalid indices or authorization, but for a read tool it conveys the key behavioral traits.

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 three sentences, each adding distinct value: purpose, pagination behavior, and a usage tip. It is front-loaded and contains no redundancy or filler, making it easy for an agent to parse quickly.

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 tool's moderate complexity (4 params, no output schema, no annotations), the description effectively covers the essential semantics: what it returns, how to paginate, and when to use it. It explains the default behavior and the relationship between the parameters, providing enough context for an agent to invoke it correctly without additional documentation.

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?

The schema covers all parameters with descriptions, so the baseline is 3. The description adds meaning by clarifying that 'chapter' is an index from list_chapters, explaining the 'maxChars' default and cap, and showing how 'offset' relates to 'nextOffset' for pagination. This elevates it beyond mere schema repetition.

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 'Return the plain text of one chapter/section by its index', which uses a specific verb and resource, clearly distinguishing it from sibling tools like list_chapters (which lists) and get_book (which gets a whole book). It also sources the index from list_chapters, reinforcing the intended use.

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 clear context by indicating the chapter index comes from list_chapters and gives explicit paging instructions for long chapters. It lacks an explicit 'when not to use' or direct naming of alternative tools, but the guidance 'Read only what you need' implies selective retrieval, and the paging advice is practically useful.

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