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

With no annotations, the description carries the behavioral burden. It discloses useful traits — cost ('FREE'), result cap ('top 3'), and scope ('open and forecasted US federal grants') — but says nothing about rate limits, authentication, result fields, or pagination, which would help an agent invoke it confidently.

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, front-loaded sentence with zero waste. 'FREE' and the result cap are surfaced immediately, and no sentence is extraneous.

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?

For a simple one-parameter search tool with no output schema and no annotations, the description provides the essential context: cost, coverage, keyword examples, and result count. It could be more complete by explicitly routing users to grant_search_full for exhaustive results, but nothing critical for a basic invocation is missing.

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 0%, so the description must compensate. It does so by explaining that the single required parameter is a keyword and providing concrete examples ('broadband', 'small business', 'opioid'), which meaningfully clarifies expected input beyond the bare string type.

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 states a specific verb and resource: searching open and forecasted US federal grants by keyword. It distinguishes itself from grant_search_full only implicitly via 'top 3', which suggests a limited result set, but it does not explicitly name or contrast with the sibling.

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 'FREE' label and 'top 3' result limit imply this is a quick, low-cost lookup, but there is no explicit guidance on when to use this versus grant_search_full or closing_soon. Conditions for choosing alternatives are left to inference.

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