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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds behavioral value by specifying the exact output fields (name, party, chamber, bioguide ID) and the downstream use of the ID, which is helpful given there is no output schema. It does not mention pagination or ordering, but this is a minor omission for a read-only search tool.

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 sentences with no filler: the action and filters are up front, return values are stated next, and the cross-reference is last. Every clause earns its place and the structure is easy 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?

For a simple read-only search tool with no required parameters and a fully described input schema, the description covers the search filters, the return fields, and the natural next step (congress_member_details). The lack of an output schema is partially compensated by the explicit return field list, though details like pagination or result count are not addressed.

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 all five parameters and their types. The description restates the filtering semantics for Congress, state, and district but adds no new meaning beyond that; it omits the limit and current_member parameters entirely. A 3 is the appropriate baseline when the schema carries the parameter documentation burden.

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 uses a specific verb ('Search') and resource ('members of Congress'), and enumerates the optional filters and return fields. This clearly distinguishes it from congress_search_bills and congress_member_details, so an agent can tell what the tool is for without inspecting the 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?

The description establishes a clear use case: searching members by optional filters rather than retrieving details for a known member. It also gives a concrete routing hint by saying the returned bioguide ID should be used with congress_member_details. It does not explicitly exclude bill searches or other sibling tools, but the context is sufficient.

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