Read Chapter

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

With no annotations provided, the description carries the full behavioral burden. 'Read the full content' strongly implies a non-destructive, retrieval operation, which adds some behavioral transparency. However, it does not mention response characteristics, auth or access constraints, or any edge-case behavior like locked or unavailable chapters.

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 a single efficient sentence with no filler, front-loading the verb and object. It is appropriately sized for a simple tool with two well-documented parameters and an output 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?

The tool is simple and the output schema exists, but the description leaves sibling differentiation to inference. An agent might confuse `read_chapter` with `get_chapter_list` without further guidance. The description is minimally adequate but has a clear gap: no explicit routeing among the five sibling tools.

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%, with both `book_id` and `chapter_id` already explained in the input schema. The description itself adds no parameter-level detail, so the baseline of 3 is appropriate: the schema does the work, and the description does not conflict or expand on it.

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 uses a specific verb ('Read') and a specific resource ('a chapter') and is not a tautology. It clearly tells the agent this tool retrieves full chapter content, though it does not explicitly differentiate itself from sibling tools like get_chapter_list.

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?

Usage context is implied: if you need the full content of a chapter, this is the tool. There is no explicit statement about when to prefer this over get_chapter_list or get_novel_info, and no exclusions are mentioned, so the guidance is present only by inference.

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