congress_committee_reports

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

Annotations already declare readOnlyHint=true, and the description does not contradict this. It adds domain context (formal reports, committee intent) but does not disclose additional behavioral traits such as pagination, rate limits, or response structure beyond what annotations provide.

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 two sentences: first defines the tool and its importance, second lists key filters. No redundancy, highly front-loaded, and every word adds value.

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 the complexity (6 optional parameters, no required, no output schema), the description adequately covers the tool's purpose and filters but lacks information on return format, pagination behavior (default limit not explained), or how results are ordered.

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%, so baseline is 3. The description adds value by explicitly enumerating report type values (hrpt, srpt, erpt) and explaining the conference report flag, reinforcing the schema and guiding correct parameter use.

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 'List committee reports' with a specific resource and includes the domain context of formal reports accompanying legislation. It distinguishes itself from sibling tools like congress_committee_details by focusing on reports and their legislative history role.

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 implies usage for understanding committee intent and legislative history, and lists filter parameters (congress, report type, conference flag) but does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives like congress_committee_details or congress_bill_details.

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