search_notices

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

Adds context about notices being 'redacted' and 'cached' and filters being 'bounded', which goes beyond the schema. However, with no annotations, it fails to disclose important details like pagination behavior, rate limits, or whether the operation is read-only.

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 one-sentence description is economical and front-loaded, but it sacrifices substance; 'bounded filters' is vague. It is not verbose, so it earns a high but not perfect score.

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?

Despite having an output schema, the tool lacks any parameter documentation, annotations, or usage context. For a 6-parameter search tool, this is incomplete; an agent needs more info about date formats, limit behavior, and category values.

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 has 0% description coverage, and the description's 'bounded filters' is too generic to clarify the six parameters. No per-parameter semantics are provided, so an agent cannot infer how to construct a query.

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 for notices, specifying they are 'redacted cached' and 'bounded filters'. This distinguishes it from sibling tools like 'list_latest_notices' and 'get_notice', which imply listing or fetching single notices.

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?

No guidance is provided on when to use this tool versus alternatives. The description only states what it does, not when to prefer it; sibling names hint at different behaviors but there is no explicit direction.

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