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

Annotations only declare the safety profile (readOnly/idempotent/openWorld), while the description adds genuinely new context: the data source (public-domain congress-legislators, explicitly not GovTrack), that it is refreshed periodically rather than live, and that data_as_of reflects the source's own last-update date. That freshness caveat is exactly the kind of behavioral detail an agent needs and cannot infer from schema or annotations.

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 user questions this tool answers, then scope, then the alternative, then provenance — a sensible ordering with little waste. The aside about GovTrack lacking a committee-leadership endpoint is defensible disambiguation but slightly padded.

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, so the description carries the burden of describing returns, and it does: chair and ranking member with name, party and bioguide id, plus the data_as_of field. For a single-optional-parameter read tool, nothing an agent needs to call it correctly is missing.

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 description coverage is 100% and the schema already lists the 'house'/'senate'/'joint' values and the omit-for-all behavior, so the description largely restates it. It adds no syntax or edge-case detail beyond the schema, making the baseline 3 appropriate.

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 resource (every standing committee in a chamber with chair and ranking member) and the exact question shapes it answers, so an agent can match intent immediately. It also distinguishes itself from the closely named siblings committee_members and member_committees by scoping itself to the chair/ranking pair only.

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?

Explicit routing: 'For one committee's FULL roster ... use committee_members instead', plus a direct instruction on how to use the chamber parameter (pass to scope, omit for all three). Both the when-to-use and the when-to-use-something-else conditions are stated.

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