Get Recent Congressional Votes

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

Annotations already indicate readOnlyHint=true, so the description adds value by disclosing the data source (GovTrack), current bias ('currently Senate-heavy'), and the content of each vote (member, bill info, position, result). This provides behavioral context beyond the annotation.

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 long, with the first sentence clearly stating the main purpose and the second detailing the output. Every word is necessary, and it is front-loaded with key information.

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 presence of an output schema, the description adequately covers what the tool returns. It mentions the data source and a caveat (Senate-heavy). However, it could be slightly more complete by explicitly noting that only recent votes are returned and that House votes may be limited.

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% for the two parameters (limit, offset), so they are already documented. The description does not add further meaning about parameters, so it meets the baseline expectation.

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 states the tool gets 'recent congressional roll-call votes across all members', specifying the verb 'get' and the resource 'recent congressional roll-call votes'. It distinguishes from siblings like 'get_politician_votes' by noting 'across all members' and mentioning the source GovTrack and both chambers.

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 provides no guidance on when to use this tool versus alternatives, such as 'get_politician_votes' for a specific politician or 'get_legislative_calendar' for calendar data. No when-not or alternative tools are mentioned.

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