congress_member_details

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

The description discloses exactly what data is returned (full bio, party history, all terms, committee assignments, photo URL, official website) which is not available in the annotations or schema. It aligns with the readOnlyHint annotation (no mutation implied) and adds specific behavioral detail about the response contents.

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: the first clearly states purpose and return contents, the second provides a helpful prerequisite. It is concise, well-structured, and every sentence adds value without 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 tool with a complete input schema, the description effectively covers what the tool does, what it returns, and how to get the required ID. No output schema exists, but the return contents are listed in the description, making the tool's behavior fully understandable.

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 single parameter bioguide_id is fully documented in the schema with a description and example. The tool description also mentions 'BioGuide ID' in the opening line, reinforcing the parameter's meaning. With 100% schema coverage, the baseline of 3 applies; the description adds no extra semantic detail about the parameter itself beyond the workflow tip.

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 opens with 'Get detailed information about a specific member of Congress by BioGuide ID,' which clearly states the action and resource. It then lists the specific data fields returned (bio, party history, terms, committee assignments, photo, website), setting it apart from sibling tools like congress_member_bills and 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?

The description explicitly instructs to 'Use congress_search_members first to find the BioGuide ID,' providing a concrete prerequisite and workflow. While it does not mention alternatives like congress_member_full_profile for comprehensive profiles, the guidance is sufficient for the primary use case.

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