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

The description meaningfully extends the readOnlyHint/openWorldHint/idempotentHint annotations by disclosing that date filters apply to summary update time rather than bill action date, which can return recently rewritten summaries of older bills. It also clarifies that each item displays both the action date and the summary update date.

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 four sentences with no filler: it states the resource and use case, clarifies an important behavioral nuance, states defaults, and routes to the alternative tool. Every sentence contributes necessary decision-making information.

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 six optional parameters, full schema coverage, rich annotations, and an output schema, the description provides the additional context an agent needs: update-time semantics, default date range, and the alternative for targeted single-bill lookup. No critical behavioral gaps remain.

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%, so the baseline is 3. The description adds value by explaining the semantic of fromDateTime/toDateTime (update time, not action time) and the default behavior, which is not fully obvious from the schema alone.

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?

States a specific verb and resource: "Browse recent CRS bill summaries" and clarifies their utility for answering 'what's happening in Congress?'. It explicitly distinguishes itself from congressgov_bill_lookup, which is the sibling for summaries of one specific bill.

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?

Provides clear when-to-use context (recent summaries, plain-language legislative stage overviews) and explicitly names the alternative tool for single-bill summaries. It also explains the default 7-day window, which helps an agent decide whether this tool fits the query.

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