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

Annotations already cover the read-only and open-world profile, and the description adds genuinely non-obvious behavior: the shape of returned items and the special second item for senators carrying checkedAt, latestVoteDate and stale. That staleness signal is exactly the kind of caveat an agent needs and cannot get from 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?

Three short sentences, front-loaded with purpose then return shape then the senator caveat. The field enumeration is slightly listy but each sentence carries real information; nothing is padding.

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 carries the burden of describing returns and does so field-by-field, including the unusual senator staleness item. Minor gaps remain around ordering and whether the list is paginated or hard-capped at limit.

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 bioguideId, chamber and the limit bounds are already fully documented in the schema. The description adds nothing about parameter behavior (e.g. that limit caps the 'recent' window, or sort order), so baseline 3 applies.

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?

States a specific verb and resource: 'Get a legislator's recent voting record,' and enumerates the returned fields. It is clear what the tool does, but it never distinguishes itself from the sibling get_vote_record, so an agent must open both schemas to choose.

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?

Usage is only implied by the word 'recent' and the required chamber/bioguideId pairing. There is no explicit when-to-use or when-not-to-use guidance, and the obvious alternative (get_vote_record) is never mentioned.

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