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

Annotations already mark the tool as readOnly, idempotent, and non-destructive, so there is no safety contradiction. The description adds useful behavioral context by listing what the profile includes (party history, terms served, leadership roles), which is especially valuable because there is no output schema.

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?

Single sentence, front-loaded with the verb and resource, then the ID format example and returned content. Every clause adds information; there is no filler or redundancy.

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 one-parameter read-only lookup with no output schema, the description gives the agent everything essential to invoke it correctly: required ID, an example, and the shape of the result. It does not mention error behavior or how to obtain an ID, but that is not essential for selection and invocation.

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%; the schema already describes bioguide_id and provides the same example. The description repeats the example but adds no further semantic detail, so the schema carries the burden and 3 is the appropriate baseline.

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?

Description uses a specific verb ('Get') and resource ('detailed profile for one member of Congress'), and clearly identifies the key identifier (bioguide ID) with an example. It distinguishes itself from sibling search tools like congress_search_members by indicating this is a single-member detail lookup.

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 clearly implies the right use case: use when you already have a bioguide ID and want a single member's detailed profile. It does not explicitly name alternatives or exclusions, such as using congress_search_members to first find the bioguide ID, so it stops short of the highest bar.

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