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

Annotations already cover readOnly/idempotent/non-destructive, so the description's added value is the 'as extracted' caveat (text may be extraction artifacts) and the citation contract requiring sha256 plus PDF page plus exact words. That is real behavioral context an agent needs before quoting. It stops short of describing pagination limits or error behavior, though the schema covers page/pages.

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?

A single front-loaded sentence with no filler, but the dense colon-chained clause about quoting makes it slower to parse than it needs to be.

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 and annotations carrying the safety profile, the description only needs to convey intent and the extraction/citation contract, which it does. Minor gaps around behavior for invalid documents or empty find results are handled by the schema and output schema rather than the prose.

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%, with defaults, ranges and find/page interaction all documented in the schema. The description only reinforces the citation use of revision sha256 and page numbering, adding little beyond structured fields, so the baseline 3 applies.

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) and resource (a revision of a modeled USPS document) with the scoping detail 'page by page, as extracted, to quote it'. That framing separates it from search-style siblings like search_documents, but it never names an alternative explicitly.

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 phrase 'to quote it' implies the tool's purpose (retrieving verbatim text for citation) and the citation contract hints at how to use results. There is no explicit guidance on when to prefer this over search_documents or lookup, and no stated exclusions.

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