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

Annotations already establish the tool is read-only, idempotent, and non-destructive. The description adds that results include vote number, question, result, and date, and that the congress parameter defaults to the current Congress. It does not specify ordering or pagination beyond limit, but that is a minor gap given the read-only profile.

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?

A single sentence front-loads the verb and resource, then packs a compact field list and default behavior. No filler.

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?

For a simple read-only list with two optional parameters, the description plus schema covers input and expected output fields. The absence of an output schema is partially mitigated by listing returned fields; ordering and pagination semantics remain unspecified but are minor.

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 defaults and meaning of limit and congress are already documented. The description only restates the current-Congress default and does not add format or syntax details, so baseline 3 is appropriate.

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 action ('List') on a specific resource ('U.S. House roll-call votes') and names the returned fields. The tool is clearly distinct from sibling Congress tools such as bill details or recent laws.

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 makes the primary use case explicit: retrieving recent House roll-call votes, optionally filtering by Congress and limit. It does not explicitly name alternatives or exclusions, but there is no overlapping sibling tool for roll-call votes, so the context is clear.

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