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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description still adds substantive context: the counts are self-computed rather than an official score, no percentile/rank is produced, an API key is required, and the bipartisan figure is derived only from the newest bills_analysed sponsored bills — a real sampling caveat that affects interpretation.

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?

Front-loaded with the questions it answers, which is the right ordering for retrieval, and every clause carries information (metrics list, sampling caveat, GovTrack disclaimer, API key). The single dense sentence is packed tightly, and the metric enumeration could be broken out for faster scanning.

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 2-param read-only tool with no output schema, the description effectively enumerates the returned metrics (sponsored, cosponsored, became law, bipartisan share), names the data source, and flags the key requirement — enough for an agent to call it and interpret results without further context.

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% and both parameters are documented in-schema (congress default, bioguide_id source). The description reinforces the scoping constraint that statistics are computed for exactly one member and one Congress, which clarifies that congress is a scope limiter rather than a filter across members.

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+resource: legislative activity statistics for ONE member in one Congress, enumerated as sponsored/cosponsored/ enacted/bipartisan counts. It is clearly distinguished from siblings like get_members (roster lookup) and search_bills (bill search), and explicitly disclaims being GovTrack's report card.

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 three example questions ("how many bills has Rep. X sponsored", "how bipartisan is Senator Y", "what share of X's bills have other-party cosponsors") give concrete trigger conditions, and the GovTrack exclusion tells the agent when this is NOT the right source. It stops short of naming a direct alternative sibling for member-level queries, so not a full 5.

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