congress_committee_meetings

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

Annotations provide readOnlyHint=true, so the description's addition of listing dates, locations, and topics adds behavioral context. However, it does not disclose pagination behavior, rate limits, or what happens if no results match.

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 a single concise sentence followed by a short filtering note. No redundant information, and the key purpose 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?

With no output schema, the description hints at return fields (dates, locations, topics) but does not mention pagination via the 'limit' parameter or ordering. It is adequate for a simple list tool but lacks full completeness for an agent to predict exact behavior.

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 mentions filtering by congress and chamber but does not add meaning beyond the schema for fromDateTime, toDateTime, or limit. The schema already provides clear descriptions for each parameter.

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 it lists committee meetings (hearings, markups, etc.) with dates, locations, and topics. It distinguishes from sibling tools like congress_committee_meeting_details (specific details) and congress_hearings (maybe just hearings) by using a general 'List' verb and specifying the types of meetings.

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 says 'Filter by congress and chamber', implying usage for general listing, but does not explicitly state when to use this tool versus alternatives (e.g., congress_committee_meeting_details for a single meeting). No exclusions or when-not guidance.

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