gov.bill-summaries

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

With no annotations provided, the description fails to disclose behaviors like pagination, response format, rate limits, or data freshness. It only states the data source and filter options, leaving significant gaps for agent usage.

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 two concise sentences with no filler. The first sentence defines the tool's purpose, and the second adds filter capability. Every word adds value.

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 7 parameters, no output schema, and no annotations, the description is insufficient. It does not cover pagination, sort options, or response structure, leaving the agent underinformed for proper usage.

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 0%. The description explains 3 of 7 parameters (congress, type, date range) but omits sort, limit, offset, which are crucial for controlling output. Missing parameter semantics hamper correct invocation.

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 it provides 'Latest US Congressional bill summaries (CRS-authored, attached to specific bill versions) via Congress.gov.' This distinguishes it from sibling tools like gov.congress-bill (bill details) and defines the scope precisely.

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 mentions filtering by congress, type, and date range, but does not explicitly specify when to use this tool versus others (e.g., gov.congress-bill for full text). Usage context is implied rather than explicit.

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