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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds value by listing the return fields (title, sponsors, etc.), but does not elaborate on pagination, rate limits, or other behavioral traits. Given strong annotations, this is adequate.

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 efficient sentences: first states action and parameters, second lists return fields and source. No redundant content; every word earns its place.

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 the output schema exists and the tool is a straightforward read lookup, the description covers core aspects. The only gap is the incomplete type specification, which is partially addressed by the schema. Overall well-rounded.

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 schema descriptions are thorough. The description correctly notes congress and number but simplifies type as 'hr/s' whereas the schema includes eight types (e.g., hjres, sjres). This is misleading and adds negative value despite high schema coverage.

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 retrieves full details for a specific US bill, specifying the three parameters (congress number, type, bill number) and listing returned fields (title, sponsors, action history, etc.). This distinguishes it from sibling tools like 'congress.legislation.bills' (likely a list) and 'congress.legislation.members'.

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 usage when you have a specific bill identified, providing clear context. However, it does not explicitly state when not to use it (e.g., for searching or listing) or mention alternatives, which would elevate it to a 5.

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