congress_search_members

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds the endpoint patterns but does not disclose additional behavior like pagination, default limit, or response format, so it provides limited extra transparency.

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 concise with two sentences. The first sentence front-loads the core purpose ('Search for members of Congress'), and the second lists the supported patterns efficiently.

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?

The description covers the main use cases but omits details like pagination (limit parameter), date filtering, and the structure of returned data. While the schema covers parameters, the description could benefit from mentioning result limits or the 'currentMember' filter.

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?

The input schema has 100% description coverage for all 7 parameters, so the schema already explains parameter purposes. The description only restates the endpoint patterns, adding no new semantic information beyond the schema.

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 clearly states it searches for members of Congress using various criteria (state, congress, district, etc.) and lists the supported endpoint patterns. This distinguishes it from sibling member detail tools like congress_member_details.

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 usage scenarios through the listed endpoints (e.g., 'get all current members', 'by state'), but does not explicitly state when to use this tool versus alternatives like congress_member_details or congress_member_full_profile.

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