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

The description asserts 'Read-only,' while annotations declare readOnlyHint=false — a direct contradiction on the most important behavioral trait. The fee-split sentence adds economic context but does nothing to resolve whether the call mutates state or is safe to retry (idempotentHint=false).

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?

The lead clause front-loads the resource, which is good, but the closing sentence about retirement revenue splits is irrelevant to deciding whether and how to invoke the tool. The two-word 'Read-only.' claim is both wasteful and actively misleading given the annotations.

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 return values need not be explained, and with zero parameters the call surface is trivial. What remains missing is the essential bit — what the tool actually does — plus a contradiction with annotations that could cause an agent to treat a non-read-only call as safe.

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 takes zero parameters, so there is no parameter semantics to explain; the baseline for a no-arg tool is 4. The provenance fields mentioned (project id, serial, vintage) describe returned data, not inputs.

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 ('the tradeable Verra VCS book' of credits with project id, serial, vintage), so an agent can tell roughly what domain it covers. But it is a noun phrase with no verb: it never says whether the tool lists inventory, returns a summary, or prices the book. With siblings like 'book' and 'list_credit' in the same family, the boundary is not established.

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?

There is no statement of when to call this versus alternatives — not even versus the obviously adjacent 'book' or 'list_credit' tools. The only conditional sentence ('Every retirement nets the project 85%...') describes a business rule, not invocation guidance.

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