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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds real behavioral detail: output is chunked page by page with '[Page n]' markers, long documents can be continued or bounded with a page range, and a range of document formats is handled. It omits failure behavior (e.g., missing document_id) and any size limits.

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 compact sentences, front-loaded with what is returned and followed by practical continuation advice; nothing is padded. Minor readability cost from stacked parentheses and nested quotation marks around '[Page n]'.

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 3-parameter read tool with no output schema, the description does useful work by describing result shape (per-page text with markers) and continuation semantics. It is still incomplete on how to obtain a valid document_id, on error behavior, and it leaves the meaning of 'next_start_page' ambiguous, which matters because it looks like a callable parameter.

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 description coverage is 0%, so the description carries the burden of explaining all three parameters. It does convey that start_page/end_page form a page range and that document_id identifies the document, but it never states what document_id actually is (an integer ID obtainable from list_documents) or any constraints, and it introduces 'next_start_page' which is not a parameter at all.

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 resource (text of a document) and scope (page by page, with '[Page n]' markers), plus supported formats, which lets an agent tell it apart from get_document_stats or list_documents. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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 gives a use context ('so you can answer questions about it or summarize it') and pagination guidance for long documents, which is genuine when-to-use help. However, it never says when to prefer this over siblings such as get_document_stats or fetch, and the pagination advice points at 'next_start_page', a name that is not in the input schema, which could mislead an agent into trying to pass it.

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