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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond annotations: the page-at-a-time access pattern, the citation-focused return value ('page text with the page numbers needed to cite it'), and the dependency on a prior list/search call.

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 sentences with zero redundancy: the first delivers the action, scope, and input prerequisite; the second delivers the return value. The most important information (verb, resource, pagination behavior) is front-loaded.

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 paginated fetcher with rich annotations, full schema coverage, and no output schema, the description is complete: it states the return shape (page text with page numbers), the input source, and the access pattern. Minor gaps like end-of-document behavior when requesting more pages than exist do not impede correct invocation.

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 100%, so all three parameters are already documented in the schema. The description reinforces doc_id's provenance ('from epstein_list_documents or a search result') but adds no meaningful semantics beyond what the schema already states, so the baseline 3 is appropriate.

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 names a specific verb ('Read'), a specific resource ('the full text of one document from the House Oversight Epstein investigation'), and a clear access pattern ('a page at a time'). It distinguishes itself from the sibling tools epstein_list_documents and epstein_search_documents by requiring an existing document id as input, so an agent can immediately tell retrieval-from-listing apart.

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 'given the document id from epstein_list_documents or a search result' explicitly states the prerequisite workflow: list or search first, then retrieve. This gives clear context for when to invoke the tool, though it stops short of explicitly naming alternatives or stating when-not-to-use it.

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