reading_continue

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

Annotations already declare readOnlyHint=true, indicating no mutation. The description adds behavioral detail beyond annotations by explaining the fallback logic for omitted bookId, which is not captured in the schema or annotations. This is valuable for understanding tool behavior.

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 two succinct sentences with no extraneous information. Every word adds value, directly addressing purpose and parameter behavior.

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 simplicity (one optional parameter, no output schema), the description is largely complete. It explains the core function and parameter behavior. However, it does not describe return values or the format of the 'chunk', which could be inferred but is not explicit.

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 sole parameter 'bookId' has no description in the schema (0% coverage). The description fully compensates by explaining its optionality and default behavior, providing clear semantics that enable correct invocation.

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 clearly states the tool's purpose: 'Continue reading from the next unread chunk', specifying verb (continue reading) and resource (unread chunk). It distinguishes from siblings like 'reading_read_chunk' by implying automatic progression rather than reading a specific chunk.

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 usage context: 'If bookId is omitted, use the most recently read book.' This tells the agent when to use this tool (to continue reading) and how the optional parameter works, though it does not explicitly exclude alternative tools.

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