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

No annotations exist, so the description carries the full burden. It does disclose useful traits — default window of 30 days, ascending deadline sort, restriction to 'posted' grants, and (via the 'PRO.' marker plus the access_token param) that a subscriber credential is required — but says nothing about result limits, pagination, or behavior when no grants match.

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?

A single tight sentence with no wasted words, and the two most filtering-relevant facts (keyword scope, N days) come first. Leading with the opaque 'PRO.' tag is mildly wasteful, but the rest is efficiently front-loaded.

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 annotations and no output schema, the description is the only specification an agent has, yet it omits keyword matching semantics and any hint of result size or pagination. For a three-parameter pro search endpoint that is too thin to call confidently.

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 only 33%, so the description must compensate. It clarifies within_days (window size, default 30) but leaves keywords undefined — no indication of whether terms are ANDed, ORed, or matched against title, funder, or abstract — which is the single most consequential input for a search tool.

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 pairs a specific resource (posted grants matching your keywords) with a specific scope (closing within N days) and states the ordering (soonest first), which goes well beyond the bare name 'closing_soon'. It does not name the sibling tools (grant_search, grant_search_full), so an agent must infer the distinction from scope alone.

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?

There is no explicit when-to-use or when-not-to-use guidance relative to grant_search or grant_search_full, and no statement of prerequisites beyond the cryptic 'PRO.' prefix. The deadline-tracking intent is implied by the name and the 'within N days' phrasing but never spelled out as a selection rule.

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