congress_summaries_search

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

Annotations show readOnlyHint=true, and the description adds behavioral context: sorting by last update date and results including bill reference. Does not contradict annotations, but could mention pagination or default limit. Still adds value beyond annotations.

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?

Concise three-sentence description. Front-loaded with main purpose and key distinction. No unnecessary words, all sentences add 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?

Describes search scope and result inclusion of bill reference, but no output schema means the description should clarify more about return fields, pagination, or error handling. Lacks detail on limit parameter behavior and result structure beyond bill reference.

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 baseline is 3. Description mentions filtering by congress, bill type, and date range, aligning with parameters, and notes sorting by update date. Adds marginal context but does not deeply explain parameter semantics beyond schema.

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 searches bill summaries across all bills and congresses, contrasting with congress_bill_summaries which requires a specific bill. The verb 'search' and resource 'bill summaries' are specific, and sibling differentiation is explicit.

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?

Explicitly contrasts with sibling tool congress_bill_summaries, stating when to use this one (for broad cross-congress search) vs the other (for a specific bill). Also lists filters and sorting, providing clear usage context.

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