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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower, yet the description still adds real context: ambiguous names return both chambers as `matches` rather than guessing, results are baked periodically and cover the 119th Congress only, and the public-domain data source is disclosed. This is the kind of ambiguity and freshness behavior an agent needs and that no annotation provides.

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 answering queries, and every clause carries routing or behavioral information. The single dense paragraph and stacked parentheticals make it slightly heavy to scan, but there is little waste to cut.

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?

With no output schema, the description carries the burden of describing the return shape, and it does: member party/rank/title, committee chair and ranking member, and subcommittee list. Combined with source, freshness, and ambiguity behavior, an agent has everything needed to call and interpret the result.

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%, so the baseline is 3; the description goes beyond it by supplying subcommittee-id examples ('HSWM05'), the full committee_id format, and the name-matching/chamber-disambiguation semantics in narrative form. It largely repeats the schema's 'takes priority over name' note, which keeps it from a 5.

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?

Opens with three concrete example queries ("who is on the House Appropriations committee") and states exactly what is returned: one committee's full membership with party, rank, title, plus chair, ranking member and subcommittees. It explicitly distinguishes itself from committee_leadership and, by implication, from member_committees (the inverse lookup). An agent can route correctly without opening either sibling 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?

Gives explicit selection conditions: use committee_id OR name, pass chamber to disambiguate a name matching both chambers, and use committee_leadership instead when only chairs/ranking members of every committee are needed ('it is cheaper when you do not need the full roster'). Both the when-to-use and the when-not-to-use alternative are named.

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