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

No annotations are present, so the description carries the burden. It does reveal the HTTP method/endpoint, filter behavior, and the fact that responses contain committee_id values needed by get_committee. Still, it omits details like output item shape beyond the ID, pagination behavior, or auth requirements, so it is only partially transparent.

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?

One concise sentence states the action, endpoint, filters, and output purpose, front-loading the core behavior. No filler or redundancy.

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 read-only list tool with four optional parameters and no output schema, the description covers what it returns (committee_ids) and how it can be filtered, which is enough to invoke it correctly. It does not describe full response rows or usage edge cases, but the schema covers parameter limits and defaults.

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?

With 100% schema coverage, the schema fully documents q, limit, state, and chamber, so the description doesn't need to repeat definitions. The description adds only a high-level mapping ('jurisdiction, chamber, or name search') that aliases state/chamber/q. That meets the baseline but adds no concrete nuance beyond the schema.

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 opens with a specific verb ('List') and resource ('legislative committees'), identifies the REST endpoint, and enumerates filtering dimensions (jurisdiction, chamber, name search). It also differentiates from the sibling get_committee by noting the output supplies committee_id values, so the tool's role is unambiguous.

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 clear context: this is the listing endpoint that produces the committee_id values which get_committee consumes, which tells an agent when to call it as a precursor. It doesn't explicitly name alternatives or exclusions, but for a list tool the chaining cue is sufficient guidance.

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