congress_search_members

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about the multiple endpoint forms, but does not disclose return structure, pagination, or historical-member behavior beyond what the schema already states.

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 two efficient sentences, front-loading the core purpose and then compactly listing supported endpoint patterns. Every part earns its place, and the structured list is easy for an agent to parse.

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 rich annotations and 100% parameter schema coverage, the description does not need to repeat parameter details. It covers the main decision-relevant behavior — what search dimensions are supported and how they combine — and is complete enough for an agent to invoke the tool correctly. A minor gap is no mention of the response shape, but no output schema is provided and the search semantics make it reasonably inferable.

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 applies. The description maps parameters to URL path patterns, but the schema already explains combinations like using congress with state+district and using district with state. The description adds little semantic meaning beyond what the property descriptions provide.

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 action ('Search for members of Congress') and enumerates the exact resource scopes: state, congress number, district, and all current members. The endpoint pattern list makes the tool's scope unmistakable and differentiates it from sibling tools like congress_member_details or congress_search_bills.

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 implies when to use the tool — whenever you need member listings by state, congress, or district — and even highlights the 'all current members' mode. However, it does not explicitly name alternatives or state when NOT to use it, such as when a specific member's details are needed.

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