congress_committee_meetings

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

The annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds minimal behavioral context beyond 'list' – it does not describe pagination, sorting, rate limits, or any side effects. The mention of 'hearings, markups, etc.' is resource semantics, not behavioral transparency. No contradiction exists, but little value is added beyond the 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?

The description is two sentences with no redundant information. It front-loads the core action and resource, followed by filter capabilities. Every word contributes to understanding what the tool does.

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 is a simple list operation with no required parameters and all parameters documented in the schema. The description hints at the return content (dates, locations, topics), which is helpful given no output schema. It is adequate for an agent to invoke correctly, though more explicit mention of the distinction from sibling tools 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 description coverage is 100%, so the parameters are already fully documented. The description reinforces that filtering by congress and chamber is possible, but this is a direct restatement of the schema. No new meaning or format details are added beyond the schema, warranting the baseline score of 3.

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 verb ('List') and resource ('committee meetings') and includes what is returned (dates, locations, topics). However, it does not differentiate itself from sibling tools like congress_hearings or congress_committee_meeting_details, which could also provide meeting information. This is a clear purpose but without sibling distinction.

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?

No guidance is given on when to use this tool versus alternatives. The description mentions filtering by congress and chamber but does not explain when an agent should choose this over congress_hearings or congress_committee_meeting_details. There are no exclusions or alternative tool references.

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