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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior, and the description adds meaningful context: it returns citations, dates, congress numbers, and govinfo links, and it cautions about publishing delays and interpretation of named persons. No contradictions 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?

The description is reasonably concise and structured: it opens with the primary action, then gives usage examples, return info, and caveats in separate sentences. Each sentence adds value, though it is somewhat longer than the two-sentence ideal and could tighten the redundant 'congressional' phrasing.

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?

Given 7 parameters, no output schema, and good annotations, the description covers the key aspects: what it searches, what it returns, how to proceed to full text, and important caveats about publication delays and interpretation. It lacks explicit rate-limit or auth details, but the schema documents the API key and annotations cover safety, making this adequate for a search tool.

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 input schema already provides 100% description coverage for all parameters, so the baseline is 3. The description adds minimal parameter-level detail beyond the schema—it mentions document types in the intro but does not elaborate on query syntax, date formats, or the _apiKey parameter, leaving the schema to carry the load.

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 searches the full text of official U.S. congressional documents and enumerates the specific document types (hearing transcripts, committee reports, etc.). It distinguishes itself from sibling tools by explicitly directing users to get_congressional_document_text for reading the actual wording.

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 explicit use-case examples ('what was said in the congressional hearing about X') and warns that it only searches published documents, which implies when not to expect transcripts. It also points to the companion tool for reading full text, offering clear workflow guidance, though it does not explicitly list alternatives for other search scenarios.

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