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

With no annotations, the description carries the full burden and does disclose meaningful behavior: a per-call cost of $0.001, the x402 payment rail (USDC on Base), and that responses include a provenance chain and Ed25519 attestation. It stops short of stating error behavior, rate limits, or that this is a read-only operation.

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 tight sentences with the resource and returned fields front-loaded, followed by the cost and attestation details. Every clause earns its place, with only the dense billing clause being slightly packed.

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 correctly enumerates the returned fields, and it covers the pricing/payment model for the one parameter needing context. For a single-record lookup tool this is nearly complete, missing only id format specifics and error/not-found behavior.

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 50%, and the required 'id' parameter has no schema description at all; the description compensates by explaining it is composed of congress, type and number. The payment parameter is already documented in the schema (legacy header, omit for a free quote), and the description reinforces the paid nature. No exact id syntax/example is given, keeping it from a 5.

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 resource (US Congress bill record) and the lookup keys (congress, type, number), and enumerates the returned fields (title, sponsor, latest action, policy area, origin chamber). It is distinguishable from all siblings, none of which cover Congress bills, though it phrases purpose as a noun rather than an explicit verb.

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?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The only usage hint is the incidental note that omitting payment yields a free quote, which concerns a parameter rather than tool selection.

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