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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds useful behavioral context beyond that: it notes the tool is 'keyless' (no auth required) and specifies the return fields (opportunity number, title, agency, status, dates, CFDA). It does not mention rate limits or pagination behavior.

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 with zero waste. Purpose and keyless note are front-loaded, followed by filters and return fields. Every clause 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?

With no output schema, the description helpfully explains the return fields. Annotations and schema cover safety and parameters. It is complete for calling the tool, though it omits mention of the detail-retrieval sibling grants_get_opportunity and any pagination guidance beyond the schema's rows parameter.

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%, so the schema fully documents all 7 parameters. The description only lists some filter categories (keyword, status, agency, funding category, eligibility) without adding syntax or format details beyond what the schema already provides, so the baseline of 3 applies.

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?

States a specific verb ('Search') and resource ('federal funding opportunities on Grants.gov'), and lists the filters and return fields. However, it does not explicitly name or differentiate from the sibling tool grants_get_opportunity, so it stops short of full sibling distinction.

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?

Provides implied usage through the verb and domain context ('Search federal funding opportunities'), and notes the tool is 'keyless', which is a prerequisite. But it never states when to use this tool versus alternatives like grants_get_opportunity, nor does it give any exclusions.

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