congress_committee_full_profile

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

The description discloses key behavioral traits beyond the readOnlyHint annotation: it combines four endpoints in parallel and returns a composite profile. It also enumerates exactly what content is included (details, history, subcommittees, website, recent bills, reports, nominations), which adds transparency about the tool's scope. However, it does not discuss edge cases like missing data or pagination beyond the limit parameter, though the schema covers the limit.

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 and concise: the first paragraph front-loads the core purpose and alternatives, while the second paragraph adds an ideal-use case and cross-referencing tip. Every sentence contributes meaningful information without unnecessary filler.

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 composite read tool with no output schema, the description adequately covers what data is returned and how it differs from calling endpoints individually. It also provides usage context. Minor gaps include not explicitly mentioning the limit parameter's effect or return format, but the schema covers the parameter and the tool is straightforward for a read-only profile.

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 schema already documents all three parameters (chamber, committee_code, limit) with descriptions and an enum. The description adds no additional parameter-level detail beyond what the schema provides, so the baseline score of 3 is appropriate.

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 a specific verb and resource: 'Get a COMPLETE committee profile in ONE call.' It clearly distinguishes this tool from siblings by explicitly naming the four individual endpoints it replaces (congress_committee_details, congress_committee_bills, congress_committee_reports_for_committee, congress_committee_nominations_for_committee), making the purpose unambiguous.

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 provides explicit usage guidance: 'Use this instead of calling... individually' and 'Ideal for: Understanding a committee's jurisdiction, workload, and oversight activity.' It also suggests a cross-referencing workflow with other tools (congress_member_details, FEC, lobbying_search), giving clear context for when and how to use it.

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