congress_crs_reports

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds no further behavioral traits such as authorization needs, rate limits, or side effects. With annotations present, the description's omission is acceptable but not enhanced; thus a mid-range score is appropriate.

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 sentences with no extraneous words. It front-loads the core function ('Get Congressional Research Service reports') and includes a sentence that sells the quality of the data without repetition. Every word serves a purpose.

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?

The description explains the nature of CRS reports (authoritative, nonpartisan) and their reputation, providing context for an agent to understand the data quality. However, since no output schema exists, the description could have briefly noted what fields are returned (e.g., title, date, summary). For a simple list tool with good annotations, this is mostly complete but lacks output structure hints.

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 schema itself documents all three parameters effectively. The description adds no additional parameter-level guidance (e.g., common use cases for date filters, limit best practices). Baseline 3 is merited as the description does not detract but also does not add value beyond 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 clearly states the tool retrieves Congressional Research Service reports, using the verb 'Get' and the resource 'Congressional Research Service reports'. It distinguishes from sibling tools like congress_crs_report_details by focusing on the general collection rather than a single report, and the phrasing 'authoritative, nonpartisan analysis' adds context without ambiguity.

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 provides no guidance on when to use this tool versus alternatives like congress_crs_report_details or other search tools. It does not mention prerequisites, filter applicability, or scenarios where this tool is preferred. The lack of usage context forces the agent to infer from the purpose alone.

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