read

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

While annotations are absent, the description adds a useful constraint (up to 20 pages) and lists formats. However, it does not explain indexing, error behavior, or whether results are always read-only (though implied by the name).

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?

The description is a single, front-loaded sentence with no filler words, efficiently conveying the core action and options.

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 tool with no annotations, no output schema, and no parameter descriptions, this terse description is insufficient. An agent cannot determine how to specify page ranges or understand return structure, making the tool harder to invoke 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?

The description mentions the format options and a page limit, which loosely maps to format and page range parameters, but it does not explain document_id, page_start, or page_end semantics. With 0% schema description coverage, this leaves gaps.

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 clearly states the tool reads pages and lists supported output formats, using a specific verb and resource. It does not explicitly distinguish it from sibling tools like render, but its function is reasonably clear.

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?

The description provides no guidance on when to use this tool versus alternatives like search, grep, or render. It does not state prerequisites or typical use cases.

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