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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description adds data-currency context instead: source repo, public-domain provenance, periodic baking, and the current-119th-Congress-only scope. The current-Congress-only limitation is genuinely useful behavioral disclosure beyond the 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-loads the answer format before parameter guidance and source provenance, so the most important information comes first. It is dense and the parenthetical is long, but every clause (identifier explanation, lookup workflow, source/scope) carries information an agent needs.

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-member, single-parameter tool with no output schema, the description enumerates the returned fields and states the scope (119th Congress only) and source. Nothing needed 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 coverage is 100% and there is only one parameter, so the schema already documents bioguide_id. The description goes further by explaining what a bioguide id is (the standard Congress.gov/GovInfo identifier), giving a concrete example, and telling the agent where to obtain one.

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 verb and resource: returns every committee and subcommittee assignment for one member of the 119th Congress. It even enumerates the returned fields (committee name, chamber, rank, title) and explicitly distinguishes itself from the sibling tools committee_leadership and committee_members, so an agent can route without opening schemas.

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 a clear prerequisite workflow: if you only have a name, look the member up in committee_leadership or committee_members first to get the bioguide id. It doesn't state explicit exclusions (e.g. when you'd want committee-level vs member-level data), but the context is clear enough.

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