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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful scope detail ('all member positions', House-only coverage), but discloses nothing about auth, rate limits, or response behavior beyond what annotations provide.

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 tightly written sentences, with the core purpose front-loaded and the coverage caveat following. Every sentence earns its place, though the phrasing is slightly utilitarian rather than maximally informative.

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 adequately states what is returned (vote details plus all member positions) and its coverage limitation. The safety profile is handled by annotations, so the definition is nearly complete for a simple read tool.

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%, with session, congress, and rollCallNumber each documented in the schema. The description adds no parameter-level detail (e.g., how congress bounds interact), so the baseline 3 is appropriate since the schema carries the full burden.

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 details about a specific House roll call vote including all member positions.' This clearly tells an agent what it retrieves. It does not, however, explicitly distinguish itself from the close sibling get_voting_history, leaving some ambiguity about scope overlap.

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 note 'only House votes are available via this tool' establishes a when-not boundary (no Senate votes) and implies usage context. However, it names no alternative tool and gives no explicit guidance on when to prefer get_voting_history or other siblings.

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