Grant programmes

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral context — official links and nightly re-checking of link status — which is freshness information not available in structured fields. It does not, however, say whether the directory is paginated or filtered.

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 resource is front-loaded. Slightly under-specified rather than over-long, so it is concise but does little work.

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 read-only directory tool with annotations covering safety and no output schema, the description is adequate on purpose but incomplete on the undocumented ecosystem filter and on what the listing returns. Minimum viable, with clear gaps.

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?

There is one parameter (ecosystem) with 0% schema description coverage, and the description never mentions it or explains accepted values. The description therefore fails to compensate for the schema gap; an agent cannot tell what to pass.

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 a specific resource ('blockchain ecosystem grant programmes') and implies the listing action via 'Directory of'. It is distinguishable from siblings like list_hackathons and list_events by resource, though it never states the verb or explicitly contrasts with them.

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 when-to-use guidance, no prerequisites, and no named alternatives among the many listing siblings (list_hackathons, list_events, search_whitepapers). Usage is only inferable from the resource name.

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