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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new context: the return format is 'text' and that omitting the topic yields a listing with one-line summaries. It does not discuss size limits or pagination, keeping it just short of a 5.

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?

Front-loaded with the core action and the two modes before the longer chapter-routing guidance. Every sentence carries information, though the final routing sentence is dense and could be trimmed slightly.

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?

No output schema exists, so the description compensates by describing both return shapes (a summarized list or a text chapter) and guiding the agent to the right chapter. Nothing needed to invoke it correctly 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 coverage is 100% and the enum is fully enumerated, so the schema does the heavy lifting. The description still adds value beyond it by spelling out the omit-to-list vs provide-to-read semantics and naming which chapters matter for which tasks.

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 and resource ('Read a chapter of the Dregs manual as text') and clearly describes the dual behavior. No sibling tool overlaps, and an agent can immediately tell this is the documentation access point.

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?

Explicitly distinguishes the two invocation modes ('call without a topic to list... call with a topic to get that chapter') and gives concrete when-to-use guidance mapping each chapter (SCORING, ESCALATIONS, BADGES, CHANNELS, WEBHOOKS, SERVER_SDKS) to the task that requires reading it.

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