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

Annotations already establish a safe, closed-world read, but the description adds real behavioral detail beyond them: a two-stage matching strategy (strict all-words first, broaden only on no match) and alias resolution for public names like 'Dan Crenshaw'. It also discloses the shape of each result (position, seat, party from latest term).

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?

Three dense sentences, front-loaded with the core purpose and the downstream hand-off. Every sentence carries information, though the fallback-matching clause is syntactically heavy for the value it adds.

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?

No output schema exists, and the description compensates by naming the returned fields and the identifier to reuse downstream. Combined with a well-covered three-parameter schema, an agent has enough to invoke and chain it correctly.

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%, so the baseline is 3, but the description adds genuine matching semantics the schema does not: punctuation-independent, every query word must appear in the filed name for a strict hit. It says nothing extra about position or maxResults, which the schema already documents.

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 ('Search the tracked congressional roster by name') and immediately scopes it to the roster rather than trades or net worth. An agent can distinguish it from GetMemberTrades, GetMemberNetWorth, and the other Search* tools without opening a 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?

Clearly signals when to use it and what to do with the result: 'pass the returned exact Name to GetMemberTrades or GetMemberNetWorth.' It does not state exclusions (e.g., when to use SearchInsiders instead), so it falls short of a full when/when-not treatment.

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