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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds substantial behavioral context beyond annotations: the data source, that records are limited to current members, permanent bioguide_id keying, Library of Congress Thomas committee-code conventions, Cloudflare-protected photo URLs, and the Senate class field.

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 purpose and primary key, then moves through use cases, filter guidance, committee-code details, and output caveats. It is long but appropriately structured for a complex catalog tool. Some detail, such as the long committee-code list and photo URL note, could be trimmed, but each portion generally earns its place.

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?

Given seven parameters, full schema coverage, rich annotations, and no output schema, the description is complete enough for selection and invocation. It explains the record scope, key identifier, usage scenarios, filter behavior, committee-code conventions, and notable output caveats such as photo URL handling and Senate class.

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 schema already documents each parameter; baseline is 3. The description adds meaningful semantics beyond the schema, including committee-code taxonomy examples (e.g., HSAS, SSAF, HSAG15) and guidance to combine state + chamber + party for caucus-level queries. It stops short of adding context for every parameter, but the extra committee and combination guidance is valuable.

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 verb and resource: returns Congressional member profiles from the unitedstates/congress-legislators catalog. It specifies the scope as one current House Representative or Senator and identifies the primary key bioguide_id with an example. The scope distinguishes it from related tools like get_congressional_trades.

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?

The description gives multiple explicit when-to-use examples: committee assignments, committee chairs, caucus queries, party/state/district lookup, and enriching congressional_trades records. It also provides filter-selection guidance, such as bioguide_id for direct fetch and member_name for substring search. It does not state when not to use the tool or name an alternative sibling tool explicitly.

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