reading_read_chunk

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

The annotations already signal readOnlyHint=true, so no safety ambiguity exists. The description adds useful behavioral detail about returning prevId/nextId, but does not disclose behavior on missing chunks, invalid IDs, or whether the chunk content itself is returned alongside the navigation IDs.

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 sentence with no filler. It is front-loaded with the action and resource, and the return behavior is stated concisely. It could earn a 5 only if it also communicated usage boundaries or parameter meaning in this space.

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?

This is a simple two-parameter read operation with readOnlyHint=true and no output schema. The description gives the core behavior and a navigation-related return detail, but omits any mention of error behavior, return content format, or how this tool relates to the nearby list/read siblings.

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%, and the description does not explain the meaning of bookId or chunkId. The parameter names are suggestive, but the description adds no semantic value beyond the schema's bare string types, and the agent must assume these are the required identifiers.

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?

States a specific verb ('Read'), a specific resource ('one book chunk'), and the key return behavior ('return prevId/nextId'). This clearly distinguishes it from siblings like reading_list_chunks, reading_search_chunks, and reading_continue at a glance.

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 usage: call this when you need to read a specific chunk by IDs. However, it provides no explicit when-to-use versus alternatives, no exclusions, and no mention of sibling tools that could serve similar purposes, so the agent must infer selection criteria.

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