recent_votes

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

Discloses that votes are from recently-updated bills with embedded vote data and mentions local caching. However, no annotations are provided, and the description does not cover rate limits, authentication, or potential side effects.

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?

Two short sentences that are front-loaded with the main purpose, no redundant or extraneous content.

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 5 parameters and no output schema or annotations, the description lacks details on optional parameters, return format, and pagination. It only covers jurisdiction usage, leaving significant gaps for agent decision-making.

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 0%. The description explains the jurisdiction parameter with examples but provides no information about the other four parameters (days, limit, chamber, session), leaving the agent to infer their meaning from the schema alone.

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 tool lists recent roll-call votes, specifies the data source (OpenStates), and gives jurisdiction examples. It is distinct from sibling tools like 'recent_bills'.

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?

Provides examples of jurisdiction input and mentions the wildcard '*' for all cached jurisdictions, but does not explicitly state when not to use this tool or suggest alternatives for other scenarios.

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