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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds value beyond this by disclosing that results include verbatim text, an origin proof hash, and a citable GPO URL—useful behavioral details not present in 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?

Two sentences with no filler; the first sentence states purpose and filters, the second explains output value. Very efficient and 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?

The tool has 8 optional parameters but no output schema; the description compensates by summarizing the return type (verbatim text, hash, GPO URL). Combined with strong annotations and full schema coverage, this is sufficient for an agent to invoke correctly, though examples of param combinations would improve completeness.

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 each parameter described (e.g., bioguide_id examples, date format). The description's mention of search fields (official, topic, date range, keyword) aligns with the schema but adds no new semantic detail beyond what the schema provides. 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 clearly states the action ('Search Congressional Record floor speeches') with specific filters (official, topic, date range, keyword), and the resource is distinct from sibling tools like politics_bills_search. It uses a specific verb and names the resource and scope, making it easy to distinguish.

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 clear context for when to use the tool (searching speeches by official, topic, date, or keyword) but does not explicitly mention exclusions or name alternative tools. The lack of a 'use X instead' directive prevents a 5, but the implied usage is clear.

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