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

readOnlyHint=true already marks this as a safe read; beyond that the description discloses return composition (text with sources and images) and a pagination mechanism via nextOffset. It does not state size limits or failure behavior, but adds meaningful context over the annotations.

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 core purpose, then ID sourcing, then pagination. No filler; could arguably merge the pagination note but it is efficient and readable.

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 read-only retrieval tool with no output schema, the description covers what is returned (text, sources, images) and how to page through long content, which are the main things an agent needs. Minor gaps are error handling and whether the section parameter overrides page scope, but overall it is sufficient.

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%, so a baseline 3 applies; the description goes further by explaining where page identifiers originate (content_full or content_summary) and how offset chains from nextOffset. That is genuine meaning beyond the schema's per-field text.

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 states a specific verb-and-resource relationship: it returns a page or a page+section as text with sources and images. It also distinguishes its two modes (page vs page+section) by mapping them to the page and section parameters, so an agent can tell which sibling (content_full, content_summary) produces the IDs it consumes.

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 implies the workflow: get identifiers from content_full or content_summary, then call this, and continue long text by passing nextOffset into offset. However, it never explicitly says when to choose this over content_full or when not to use it, leaving some inference to the agent.

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