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

With no annotations provided, the description carries the full transparency burden alert. It discloses that this is a one-call GET operation and describes the behavioral output in terms of participation, party-line alignment, bills sponsored/passed, and notable votes. It does not go into response format, pagination, or error behavior, but for a simple read-only lookup the provided behavioral context is reasonably rich.

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?

The description is compact and front-loaded: the first sentence identifies the endpoint and what it returns, the second gives use cases, and the third gives parameter sourcing. Every sentence adds value, with no filler or redundant restatements.

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 tool with no output schema, the description provides enough context for an agent to call it correctly: the endpoint, the required people_id, where to find that ID, and a summary of the returned information. It could optionally mention how the scores are calculated or whether filters apply, but these are not essential for invocation.

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?

The schema already documents people_id as 'people_id from list_legislators', and the description reinforces and extends this by specifying how to obtain it: list_legislators with q=name. This adds meaningful retrieval guidance beyond the schema, though the parameter itself is simple and well-covered.

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 and resource: it returns a legislator's voting and sponsorship scorecard. The description goes beyond the title by enumerating the profile contents (participation, party-line alignment, bills sponsored and passed, notable votes) and explicitly labels this as the tool for 'how does X vote' or 'is X effective', making its role distinct from sibling tools like get_legislator.

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?

Provides clear context for when to use the tool by mapping natural-language queries ('how does X vote', 'is X effective') to this tool. It also gives a concrete prerequisite and source for the parameter: get people_id from list_legislators using q=name. It does not explicitly state when not to use it or name alternatives, but the guidance is sufficient for correct selection.

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