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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds genuinely new context: it is a 'one-call' aggregate that returns several derived metrics in a single response, plus the underlying endpoint. With no output schema, this enumeration of returned metrics is the agent's only signal about result shape.

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 dense sentences: capability plus return contents first, intent routing and ID resolution second. Nothing is redundant with the title, and no sentence could be removed without losing information.

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 single-parameter read tool with no output schema, the description covers purpose, contents, and ID resolution adequately. It stops short of saying what period the scorecard covers (current session vs. career) or how the alignment metric is computed, which are the remaining questions an agent might have.

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 the schema already says 'people_id from list_legislators', so the baseline is 3. The description adds a small but real operational detail beyond that — the '(q=name)' hint for resolving the ID — which speeds up the dependent lookup.

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 ('voting and sponsorship profile for a legislator') and enumerates exactly what the profile contains: participation, party-line alignment, bills sponsored and passed, notable votes. The content enumeration also implicitly separates it from the bare 'get_legislator' sibling, so an agent can pick between them without opening a schema.

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?

Explicitly frames the intent triggers ('how does X vote', 'is X effective') and gives the prerequisite resolution path: 'Get people_id from list_legislators (q=name)'. It lacks a stated when-not or a named alternative for raw bio data, which keeps it short of a 5.

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