congress_member_full_profile

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows it is a safe read operation. The description adds that it combines three endpoints in parallel, implying performance benefits, and lists the types of data returned. It does not explicitly state rate limits or potential large response sizes, but given the annotations, this is adequate. No contradiction with annotations.

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 well-structured with a bold headline for the tool's purpose, a clear list of returned data, and a 'when to use' section with examples. It is relatively concise given the complexity of the tool. However, the latter part about 'Ideal for' could be seen as less essential, but it helps in selecting the right tool for research. No fluff, but could be slightly tighter.

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?

The tool has only 2 parameters, and the schema covers them well. With no output schema, the description does a good job of listing what data is returned (party history, terms served, committee assignments, photo, website, legislative activity). It also provides context for how to find the bioguide_id. However, it does not mention pagination or potential size of the response, but for a composite tool, this is satisfactory. The description is complete enough for an agent to call 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 description coverage is 100%, so the schema already documents both parameters. The description adds value by explaining how to use bioguide_id: it gives examples (P000197 for Pelosi, M000355 for McConnell) and tells you to use congress_search_members to find it. This goes beyond the schema's description. For bill_limit, the description says 'Max bills to return per category (default: 20)', but the schema already states that; however, the description clarifies that it applies per category. Overall, it adds meaningful context beyond the schema.

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 clearly states the tool's purpose: to get a complete member of Congress profile in one call, combining bio/details, sponsored, and cosponsored legislation. It explicitly lists what is returned (party history, terms served, committee assignments, photo, website, legislative activity) and distinguishes it from individual endpoint calls. This is a specific verb (get) + resource (complete member profile) that clearly differentiates from siblings like congress_member_details.

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 tells when to use this tool: instead of calling three individual endpoints (congress_member_details, congress_member_bills for sponsored and cosponsored) separately. It also provides ideal use cases (accountability research) and suggests complementary tools (fec_candidate_financials, lobbying_search, congress_house_votes/senate_votes). This is clear guidance on when and when not to use it.

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