congress_bill_full_profile

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which establishes the tool's safe read-only nature. The description adds that it 'Fetches 8 endpoints in parallel,' giving the agent a sense of scope and potential latency. It doesn't contradict annotations. However, it stops short of detailing response size or any rate considerations, which would be extra value. Overall, it adequately complements the annotations without redundancy.

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 informative. The first paragraph front-loads the key value proposition ('COMPLETE bill profile in ONE call') and then enumerates the included components and the parallel fetch. The second paragraph provides practical use contexts. Every sentence adds relevant information, but the description is somewhat lengthy. It could be slightly tighter, but it never wastes words. This earns a 4 rather than a 5 due to its length.

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 that this is a composite tool with no output schema, the description clearly enumerates the data domains it returns, which is essential for an agent to decide if it meets the need. It also mentions cross-referencing with other datasets (FEC, lobbying, FRED), which helps contextualize its use. However, it doesn't describe the output format or potential size, which could be a minor gap for an agent expecting a single flat object. Still, for the purpose of selecting and invoking with correct parameters, it is adequate.

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 provides 100% coverage of all three parameters (congress, bill_type, bill_number) with descriptions and examples. The description adds no additional parameter-level information, which is acceptable since the schema already fully documents them. Per the rubric, with high schema coverage, the baseline is 3, and the description doesn't need to compensate. It doesn't detract, but it also doesn't enrich 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: 'Get a COMPLETE bill profile in ONE call' and lists the included components (details, cosponsors, actions, summaries, committees, subjects, text, related bills, titles). It explicitly differentiates from sibling tools by naming the individual congress_bill_* tools and telling the agent to use this instead of calling them individually. The verb 'get' and resource 'bill profile' are specific and actionable.

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 congress_bill_details + congress_bill_actions + ... individually' and gives ideal use cases: 'Complete legislative analysis, bill research, accountability investigations, or getting everything needed to cross-reference with FEC, lobbying_search, and FRED.' This makes it clear when to choose this tool over the granular siblings, and also hints at when the alternatives might be preferred (if only one aspect is needed).

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