congress_bill_full_profile

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

The annotation readOnlyHint=true already signals a read-only operation. The description adds behavioral context by noting 'Fetches 8 endpoints in parallel' and the composite coverage, which goes beyond the annotation. It doesn't detail potential delays or failure modes, so a 4 is appropriate.

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 front-loaded main point, a clear list of included components, and a brief 'Ideal for' section. It's slightly long due to the component enumeration, but every sentence adds value, earning a 4.

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?

There is no output schema, so the description carries the burden of explaining return values. It thoroughly lists the data sections returned and the parallel fetch behavior, which gives the agent a clear picture. It doesn't specify response structure details, but for this composite profile, the description is sufficiently complete (4).

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?

All three parameters are fully documented in the input schema (100% coverage), and the description adds no additional parameter semantics—it focuses entirely on the output. The baseline of 3 is correct.

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 clear, specific purpose: 'Get a COMPLETE bill profile in ONE call' and enumerates exactly what's included (bill details, cosponsors with party breakdown, action timeline, CRS summaries, etc.). It distinguishes itself from sibling granular tools by name, listing 'congress_bill_details + congress_bill_actions...' as alternatives, making it a clear 5.

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?

It provides explicit guidance to use this composite instead of calling eight individual congress_bill_* tools, and lists ideal use cases ('complete legislative analysis, bill research, accountability investigations'). However, it doesn't explicitly state when NOT to use it (e.g., if only a single data section is needed), so it's a 4 rather than a 5.

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