govinfo_cbo_reports

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

Annotations already provide readOnlyHint=true, so the safety profile is covered. The description adds context about the source (GovInfo) and typical content (tax bill distributional analyses), but does not describe behavioral details like pagination behavior or return format. This meets the minimum bar without contradicting 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?

Two sentences: the first states the primary function and source, the second provides relevant domain context. Every word earns its place; no fluff or redundancy.

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 simple search tool, full schema documentation for both parameters, and read-only annotation, the description covers what the agent needs. No output schema means return values are not described, but this mirrors similar well-scored tools and does not create a meaningful gap.

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 100%: both 'query' and 'page_size' are documented, including an example for query. The tool description adds no additional parameter semantics beyond that, so baseline 3 is appropriate.

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?

Description uses specific verb 'Search' with a clear resource: 'Congressional Budget Office reports published through GovInfo.' It also adds a distinguishing use case about CBO scoring tax bills with distributional analysis, setting it apart from sibling tools like govinfo_search or congress_crs_reports.

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 clearly indicates the tool is for searching CBO reports, and the added context about tax bill scoring gives a concrete scenario. It does not explicitly name alternatives or when-not-to-use, but the scope is clear enough for an agent to choose this over more general GovInfo search tools.

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