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

The description adds behavioral details beyond annotations: truncation default, paging via offset, and return fields (citation, page range, URL). It doesn't contradict the read-only/idempotent hints and gives useful context about long transcripts.

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?

Four sentences with each serving a purpose: purpose, usage, return values, truncation caveat. No wasted words, well-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 tool with five parameters and no output schema, the description adequately lists what is returned and how to handle large outputs. It might miss error handling or format details, but it's largely complete.

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 covers 100% of parameters, but the description enriches understanding by linking package_id/granule_id to search results and explaining why max_chars and offset matter for long hearings. This adds value beyond the schema's basic descriptions.

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 full text of congressional documents, distinguishes it from search_congressional_documents by focusing on retrieval for quoting, and lists return components. The verb 'Read' and resource 'congressional document' are specific and unambiguous.

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 instructs to pass package_id and optionally granule_id from search_congressional_documents, establishing the workflow. It also explains how to handle truncation for long transcripts, providing practical usage guidance. It doesn't explicitly mention when not to use, but the context is clear.

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