congress_member_details

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds what data is returned but does not disclose additional behavioral traits such as pagination, missing-member handling, or relation to the full profile variant. With this annotation coverage, a score of 3 is appropriate.

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?

Two sentences, no filler. The core action and return contents are front-loaded, and the prerequisite workflow is stated in a compact second sentence. Every word earns its place.

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 single-parameter, read-only lookup tool with strong annotations, the description is reasonably complete. It lists the expected return content and the prerequisite lookup step. Since there is no output schema, the return-value summary helps compensate, though it could be slightly more explicit about behavior for unknown IDs.

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% and the one parameter is already documented with examples ('P000197' for Pelosi). The description reinforces that the parameter is a BioGuide ID and suggests how to find it, but it does not add material semantic detail beyond the schema. This meets the baseline for high schema coverage.

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 ('Get detailed information') and a clear resource ('specific member of Congress by BioGuide ID') and lists the main content returned. It clearly separates this from search-oriented tools by telling the agent to use congress_search_members first, though it does not explicitly differentiate it from similar detail tools like congress_member_full_profile.

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?

It gives an explicit prerequisite: 'Use congress_search_members first to find the BioGuide ID.' This tells the agent the correct workflow before calling this tool. However, it does not mention when to prefer this over congress_member_full_profile or congress_member_bills, so the guidance is useful but not exhaustive.

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