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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description only adds that results are 'registered' projects carrying metadata, which is modest added context with no detail on ordering, result count, or whether the list is exhaustive or truncated.

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 with no filler or repetition. It is appropriately sized for a parameterless list operation, though it is so terse that it leaves behavioral questions unanswered rather than wasting words.

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?

An output schema exists, so the description needn't explain return values, and with zero parameters and full annotation coverage the burden is low. The only missing piece is whether the list is ever paginated or capped, which matters for a 'list all' tool in a domain with sixteen siblings.

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?

This tool takes zero parameters, so the baseline of 4 applies. The description correctly makes no parameter claims and introduces no ambiguity.

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 uses a specific verb ('List') and a well-scoped resource ('all registered restoration projects with their metadata'), which is unambiguous. However, it doesn't explicitly distinguish itself from other read-side siblings like list_credit or verra_supply, leaving the agent to infer the boundary from the resource name 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?

The word 'all' implicitly signals a full-collection retrieval with no filtering, which is the primary usage cue. There is no explicit guidance on when to use this over register_project or project_funding, and no mention of whether it should be used before a detail lookup or as a discovery step.

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