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

Annotations already cover safety (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds genuinely useful behavioral context beyond annotations: it discloses that responses include a scan/no-searchable-text indicator, which matters for downstream search decisions, and specifies the output field set. No contradiction with 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?

Three tight sentences, each earning its place: what it lists, a key behavioral caveat (scans), and when to use it. The core purpose is front-loaded and there is zero filler or repetition of schema/annotation content.

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 simple list tool with a complete schema and rich annotations, the description covers purpose, output contents (compensating for the absent output schema), and usage context. Minor gaps remain: no mention of default sort order or the format of the document ids it returns, but these don't block 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 coverage is 100% — both limit and doc_type already carry full descriptions and doc_type has an enum. The description's mention of 'kind' loosely maps to doc_type but adds no filter semantics beyond the schema, 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?

The description names a specific verb+resource ('Inventory of every document held from the House Oversight Epstein investigation') and enumerates the returned fields (title, kind, page count, publication date, committee URL). It differentiates itself from siblings by noting it provides a document id for epstein_get_document and by positioning itself as the corpus overview distinct from search tools.

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 states when to use it: 'Use it to see what the corpus contains before searching it, or to get a document id for epstein_get_document.' This gives the agent a clear decision rule and names the downstream sibling tool, leaving no ambiguity about its role relative to search or retrieval.

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