congress_summaries_search

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

Annotations already declare readOnlyHint=true, so the description doesn't need to restate safety. It adds value by noting 'Sorted by last update date' and 'Results include the associated bill reference,' which convey behavioral details beyond the schema and annotations. No contradictions found.

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 five short, information-dense sentences. Each sentence earns its place: purpose, differentiation, filtering, sort order, and result content. No filler or redundancy, and the most critical information (scope and contrast) is front-loaded.

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 absence of an output schema, the description provides useful context about sort order and result contents, but it doesn't specify full return fields or pagination behavior. The limit parameter is documented in the schema, so this is a minor gap. Overall, it gives a solid understanding of what the tool does and returns.

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 mentions 'Filter by congress, bill type, and date range,' which groups parameters but adds no new semantics beyond the schema. Each parameter already has a clear description in the 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 opens with 'Search bill summaries across all bills and congresses,' clearly stating the action and resource. It explicitly contrasts with congress_bill_summaries, which requires a specific bill, thereby distinguishing this tool's broader scope from a sibling.

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 sentence 'Unlike congress_bill_summaries (which requires a specific bill), this searches CRS summaries across the entire collection' provides explicit guidance on when to use this tool versus an alternative. It also lists filterable dimensions, giving clear context for typical use cases.

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