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

With no annotations, the description carries the full behavioral burden. It does disclose that the operation is a read ('Read') and that it provides a point-in-time view ('current'), implying non-destructive behavior. However, it doesn't describe return format, response size, or any operational characteristics beyond that.

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 zero wasted words. The verb and subject are front-loaded, and every term ('current', 'Grant Search', 'coverage', 'provenance') 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?

Adequate for a zero-parameter read tool, but there are gaps: no output schema exists and the description doesn't indicate what the response will contain, nor does it clarify how 'coverage' differs from what the snapshot siblings provide.

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?

The tool has zero parameters, and the schema confirms additionalProperties: false. Baseline 4 applies since there are no parameters for the description to clarify.

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 ('Read') and resource ('current Grant Search data coverage and provenance'), making the tool's function clear. However, it does not explicitly distinguish itself from sibling tools like grant_snapshot or grant_snapshots, which could plausibly overlap in subject matter.

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?

No guidance is given about when to use this tool versus its siblings. There are no exclusions, no mention of alternatives, and no context about whether this should be checked before other grant operations.

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