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

Annotations already declare readOnly/idempotent/non-destructive, so the lower bar applies, yet the description still adds real behavior: the 118th-Congress HR/S-only coverage limit, default limits of 15 actions and 20 relationships, and that explicit stored totals plus truncation flags are returned. It does not mention auth requirements or rate limits.

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?

Two densely packed sentences with the aggregated payload up front and the coverage/defaults caveats second; almost every clause carries information. The long clause list in sentence one is heavy but not redundant.

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?

With no output schema, the description does the work of enumerating the returned fields (identity, aggregates, citations, subjects, lineage, actions, related measures, URLs, per-record hash, provenance), which is exactly what an agent needs to judge fitness. Coverage limits and truncation semantics are stated; only permission/auth and error behavior are left unaddressed.

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 bill_type, bill_number, action_limit, and response_format, making 3 the baseline. The description restates action_limit's default of 15 and adds that stored totals are always returned, but it also mentions a 'relationships to 20' bound that has no corresponding schema parameter, which could mislead slightly.

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 names a specific verb+resource (build an evidence pack for a hosted bill) and enumerates exactly what the pack aggregates: identity, sponsor/cosponsor aggregates, citations, subjects, committee path, version lineage, actions, related measures, URLs, hashes, and provenance. This composition distinguishes it from siblings like govinfo_legislation_committee_path or govinfo_legislation_version_lineage, which return only one slice each.

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?

Gives explicit trigger phrases ('build an evidence pack for H.R. 2670', 'document the source trail for S. 1') and states the applicability boundary that coverage is the complete 118th-Congress HR/S slice only. It does not explicitly say when to prefer a narrower sibling tool over this pack, so it stops short of a 5.

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