congress_committee_reports

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

The annotation readOnlyHint=true already covers the safety profile. The description adds context about what committee reports are and the filtering options, but it does not disclose behavior such as pagination, default limits (though limit is in the schema), or the shape of the returned data. Since the tool is read-only and the schema covers parameters, this is adequate but not rich.

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 consists of three concise, front-loaded sentences: purpose, filter options, and significance. Every sentence provides value, with no filler or redundancy.

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 read-only list tool with complete schema documentation and no output schema, the description adequately covers purpose, filterability, and use case. It could add information about the response format or default behavior, but the absence is not a significant gap given the annotations and schema richness.

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 has 100% description coverage for all six parameters. The description restates the filter fields (congress, report_type, conference) without adding new meaning beyond what the schema already provides, so it falls at the baseline for well-documented schemas.

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' and provides a specific definition ('formal reports accompanying legislation reported out of committee'). It does not explicitly distinguish from sibling tools like congress_committee_reports_for_committee or congress_committee_report_details, but the verb and resource are 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?

Usage context is implied through 'Critical for understanding committee intent and legislative history' and the filter options, but the description does not explicitly state when to use this tool versus alternatives such as congress_committee_reports_for_committee or congress_committee_report_details. No exclusionary guidance is provided.

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