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

Beyond the read-only annotations, it discloses the row fields returned, defines pass_rate via status codes 4, 5, and 8, and notes that committee sponsor rows are excluded by default. These are meaningful behavioral details, though it does not discuss auth, rate limits, or error behavior.

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 front-loaded with the core ranking behavior and return fields, followed by usage triggers, exclusion behavior, and the prerequisite for session_id. Every sentence contributes relevant context without repetition.

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?

There is no output schema, but the description explains the returned row fields and pass_rate calculation. Combined with the fully documented input schema and read-only annotations, an agent has enough information to invoke this tool correctly.

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 the baseline is 3, but the description adds useful meaning for key parameters: chamber filtering, sort:'passed', sort:'primary_passed' counting only carried bills, and sourcing session_id from list_sessions. It does not add much for party or limit, which the schema already documents.

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?

The description states a specific operation and resource: legislators ranked by bills sponsored and passed in one session. It also names the endpoint and distinguishes the tool as the one call for activity/effectiveness ranking, so an agent can separate it from sibling session tools.

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?

It gives concrete usage triggers such as 'who is most active or effective this session' and 'which senator passed the most bills', and explains how to set chamber and sort. It also tells the agent to get session_id from list_sessions, but does not explicitly state when not to use this tool or name a competing alternative.

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