congress_committee_full_profile

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context by explaining that this is a composite call running '4 endpoints in parallel' and that it returns recent bills, reports, and nominations. It does not mention any rate-limit or pagination nuances, but the safety profile is covered by annotations and the composite behavior is clearly disclosed.

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 front-loaded with the key value proposition ('Get a COMPLETE committee profile in ONE call') and then efficiently lists the components, the alternatives it replaces, and the ideal use case. It is slightly lengthy but every sentence contributes practical selection and invocation guidance; no 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?

Given there is no output schema, the description does a good job describing what the returned composite profile contains: committee details, recent bills, recent reports, and recent nominations. It also explains why this tool is useful and how it relates to other tools. It does not detail pagination or response structure, but those are partially covered by the schema's limit parameter and are less critical for a read-only composite endpoint.

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 input schema already covers all three parameters with 100% description coverage, including the chamber enum and a concrete committee_code example. The description does not add new parameter-level meaning beyond the schema, which matches the baseline expectation when schema coverage is full. The term 'recent' links loosely to the limit parameter but this is not elaborated.

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 a specific verb ('Get'), a distinct resource ('COMPLETE committee profile in ONE call'), and enumerates exactly what it combines: committee details, recent bills referred, recent reports published, and recent nominations referred. It differentiates itself from the four individual committee tools it aggregates, so an agent can tell it apart from siblings without needing to compare schemas.

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 says 'Use this instead of calling congress_committee_details + congress_committee_bills + congress_committee_reports_for_committee + congress_committee_nominations_for_committee individually,' naming the exact alternatives. It also gives an 'Ideal for' use case and suggests cross-referencing with other tools, providing clear when-to-use guidance.

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