congress_committee_reports

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds domain context about the content and purpose but does not disclose behaviors such as result ordering, pagination defaults, or the meaning of openWorldHint for this endpoint. No contradiction with annotations exists.

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?

Three short sentences with no filler. The first states the action, the second lists the filters, and the third gives the research context. Every sentence earns its place and the core information is 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 read-only list tool with rich annotations and a fully documented schema, the description is nearly complete. It provides the domain definition, key filters, and use-case context. It could mention what the response contains or the default congress, but these are not essential for tool selection and invocation.

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 description coverage is 100%, so the baseline is 3. The description reinforces that 'congress', 'report_type', and the conference flag are the key filters, but it adds no syntax, formatting, or default-value details beyond what the schema already provides.

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 a specific verb and resource ('List committee reports') and defines what committee reports are ('formal reports accompanying legislation reported out of committee'). It does not explicitly distinguish itself from sibling tools like congress_committee_reports_for_committee or congress_committee_report_details, but the word 'List' and the filter emphasis imply a top-level list operation.

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 when to use the tool—when you need a filtered list of committee reports for legislative history research ('Critical for understanding committee intent and legislative history'). However, it does not mention any alternative tools or when-not scenarios, so an agent is left to infer routing decisions from the name and siblings.

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