search_grants

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

No annotations are provided, so the description must convey behavioral traits. However, it only states 'search' and 'filter', without disclosing side effects, read-only nature, rate limits, or pagination behavior. The limit parameter implies pagination but is not explained.

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 a single efficient sentence with no superfluous words, delivering core purpose and key filters upfront. Every word earns its place.

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 four parameters, no output schema, and no annotations, the description lacks detail about the data source (BDNS), the nature of grant calls, expected results format, or any constraints. It is minimal and leaves the agent without sufficient context for robust usage.

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 each parameter already has an individual description. The tool's description adds contextual grouping ('filter by date range and granting body'), but this does not significantly enhance understanding beyond the schema's own descriptions. 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 clearly states the tool searches grant calls from BDNS and specifies filtering capabilities (date range, granting body). It distinguishes from sibling tools like search_grant_awards or search_legislation, which target different resources.

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?

While the description notes filtering options, it does not provide explicit guidance on when to use this tool versus alternatives such as search_grant_awards. There is no mention of exclusions or contexts where other tools would be preferred.

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