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

Annotations already establish that this is read-only, idempotent, and non-destructive, covering the safety profile. The description adds useful context about what fields are returned and requires the three identifying inputs, but it does not disclose edge-case behavior such as missing bills or rate limits. This is acceptable but not exceptional for a simple lookup.

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 sentences with no filler: the first states purpose and expected output fields, the second states the required parameters with a concrete example. Everything in the description earns its place and is front-loaded.

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 simple three-parameter read-only lookup, the description plus fully covered schema is nearly complete: it lists output contents, required inputs, and a concrete example. The only minor gap is the lack of explicit routing guidance relative to related congress bill tools, but correct invocation is not hindered.

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%, and each parameter—congress, bill_type, and bill_number—already has a clear description with enum values for bill_type. The description's example (118, 'hr', 3076) adds a small formatting confirmation but no substantive new semantics 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 opens with a specific verb and resource ('Get full detail for one bill') and enumerates the exact fields returned: title, sponsor, latest action, policy area, and cosponsor party breakdown. This clearly differentiates it from search-style siblings and from more narrowly scoped tools like congress_bill_actions or congress_bill_cosponsors.

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 implies the use case—when a specific, known bill's comprehensive details are needed—and states the required identifiers. It provides no explicit guidance about when not to use it or which sibling tool to use instead, so an agent must infer routing from tool names.

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