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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile needs no restating. The description adds genuinely new context beyond them: the result set is restricted to calls whose application window is open, and it names the fields each record carries, which matters because no output schema exists. Pagination/default behavior is left to the schema.

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 sentence with the scope constraint front-loaded and the returned fields in a compact parenthetical; no filler or restatement of the title.

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 two-parameter, no-required-argument read tool with full annotation coverage, this is close to sufficient, and describing returned fields compensates for the absent output schema. Only result ordering/total-count behavior is unaddressed, which is a minor gap.

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%, with both limit and query documented in the schema itself, so the baseline of 3 applies. The description adds nothing about query matching semantics or how limit interacts with result ordering beyond what the schema already says.

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 and resource ('List grant and funding calls') plus a real scope constraint ('currently open for applications'), and enumerates the payload fields (deadline, provider, support amount, focus areas). It does not explicitly distinguish itself from the list_* siblings, though the resource noun makes the distinction obvious.

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 'currently open for applications' clause implicitly tells the agent when this tool applies versus a general search, but there is no explicit when-to-use, no exclusion of closed/archived calls, and no named alternative (e.g. using search for keyword discovery beyond the open set).

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