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

Annotations already declare this tool read-only and idempotent, so the safety profile is covered. The description adds that it returns bill metadata and full-text availability, which is useful. However, it does not disclose search behavior such as matching rules, pagination, or whether multiple filters are combined with AND/OR, leaving some behavioral aspects opaque.

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 exactly two short sentences, front-loaded with the primary action and search dimensions. It does not repeat schema details or include fluff, making it highly efficient and easy to parse.

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 tool with no output schema, the description provides only a high-level summary of return content ('bill metadata and whether full text is available') but lacks details like default limit, pagination, or how filters interact. The description is adequate for a basic search tool but leaves several practical questions unanswered.

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 80% (four of five params have descriptions), so the baseline is 3. The description lists 'topic, sponsor, status, or congress' but does not add extra meaning beyond what the schema already states. The 'limit' parameter lacks a schema description and is not mentioned here, so the description does not compensate for that gap.

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 begins with 'Search bills by topic, sponsor, status, or congress' – a specific verb and resource with clear search dimensions. It distinguishes from sibling tools like politics_bill (likely retrieving a single bill) and politics_bill_text (likely retrieving full text) by focusing on search. Additionally, it mentions the return value, which clarifies the tool's output.

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 clearly establishes that this tool is for searching bills by various criteria, providing a clear context for when to use it (when you need to find bills by topic, sponsor, status, or congress). It does not explicitly name alternatives or exclusions, but the purpose is specific enough that the usage context is unambiguous.

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