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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world call, so the bar is lower. The description still adds real value beyond them by documenting the failure mode: a missing page returns `suggestions` containing the closest existing pages, which no annotation or schema conveys.

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?

Three short sentences, front-loaded with the action and resource, followed by usage routing and the error behavior. No boilerplate or repetition of the 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?

For a single-parameter read tool with full annotation coverage and no output schema, the description covers purpose, name-sourcing, and error recovery. The only minor gap is that the returned content's format (e.g., markdown vs. plain text) and size/pagination characteristics are not stated.

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 single `path` parameter is fully documented with examples, so the schema does the heavy lifting. The description adds the useful nuance that page names are unstable and should be sourced from search results, but no additional syntax or format detail beyond that.

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 names a specific verb pair ('fetch and extract readable content') and a specific resource ('a specific Nightbreak wiki page'), with a concrete example path. It is clearly distinguished from its sibling search_wiki, which is named as the source of page names rather than a competitor.

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?

It explicitly says page names must be taken from search_wiki results, which routes the agent correctly between the two discovery vs. retrieval tools. It stops short of an explicit exclusion such as 'do not use this when you only have a topic name', but the context is clear enough.

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