Read an offloaded page

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description goes further by disclosing the chunked/paginated access pattern, the early-termination recommendation, and the exact response fields (offset, returned_chars, total_chars, next_offset, eof) — real behavioral context beyond 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?

Two tight paragraphs: purpose first, then the operating procedure and return shape. Every sentence carries actionable information with no filler.

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?

With an output schema present, the return fields need not be enumerated, yet doing so is harmless and reinforces the paging contract. Combined with a 100%-documented input schema and readOnly annotations, an agent has everything needed to call this correctly.

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 the baseline is 3. The description adds meaning above the schema by explaining that `offset` starts at 0 and that the next call should use the returned `next_offset`, i.e. the semantics of the offset/length interplay rather than just their types.

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), resource (scraped page chunk), and qualifier (offloaded to disk) that clearly separates it from scrape/search/extract siblings. An agent can tell this is the paging reader for offloaded content, not a network-fetching tool.

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 tells the agent where the required `path` comes from ('a scrape result's `content_offloaded`') and gives a concrete loop protocol (start at 0, follow `next_offset` to `eof`). It adds a useful early-stop heuristic. It does not name alternative tools for the case where content was not offloaded, so it falls short of a full when/when-not map.

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