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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world behavior, so the safety profile is fully covered elsewhere. The description adds genuine value by disclosing return contents (award, fee, eligibility, window, deadline) and the caveat 'as the program posts it', flagging that the data reflects each program's own publishing. It does not describe result volume, sorting, or what happens when no grants are open.

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 front-loaded sentence puts the resource and scope first, then the returned fields and the optional filter. It is dense but each clause carries information; only the slightly sprawling return-field list costs it a perfect score.

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 one optional parameter, no output schema and full annotation coverage, the description supplies what the structured data cannot: what each result contains and the freshness caveat. The main omission is any clarification of borderline cases such as 'open soon' timing or empty results.

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 100% and there is only one optional parameter, so everything needed (name/code, optionality) is already in the schema. The description's 'optionally only grants open to residents of one state' merely restates the schema filter without adding format or edge-case detail, which is the baseline-3 expectation.

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 names the resource precisely (US IVF and fertility grant programs) and its scope (taking applications today, open year-round, or opening soon), which clearly separates it from the cost/coverage/clinic siblings. The verb is implicit rather than stated ('programs that...'), so it stops just short of a 5.

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 single 'Optionally only grants open to residents of one state' clause implies usage for the state filter, and the enumeration of qualifying statuses implicitly defines the selection criteria. However, there is no explicit when-to-use guidance, no exclusions (e.g., how this differs from checking employer coverage), and no routing to siblings.

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