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

With no annotations, the description carries full burden. It declares 'Read-only' (safe), explains the tool generates records for submission under the Viridis Verra account, and notes future automation ('auto-posts when Verra's transaction API is live'). This is good disclosure, though error behavior is omitted.

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 description is reasonably concise and well-structured: purpose first, then output contents, safety note, and usage instruction. However, the phrase 'portal today; auto-posts when Verra's transaction API is live' adds slight verbosity. Overall efficient.

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?

Given the tool has 2 parameters and an output schema, the description covers output hints but completely neglects input parameter documentation. This leaves a significant gap, making the tool harder to use correctly without external knowledge.

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 description does not mention the input parameters (purchase_id, retirement_reason) at all, despite 0% schema coverage. It focuses entirely on output fields, leaving the agent without guidance on what to provide or the meaning of the default for retirement_reason.

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 clearly states the tool's purpose: 'Generate the Verra-portal-ready retirement record(s) for a retirement made against Verra supply'. It lists specific output components (VCS project id, serial, vintage, etc.) and distinguishes from sibling tools like verify_retirement and verra_supply by focusing on generation of records for submission.

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 description provides context ('for a retirement made against Verra supply') but does not explicitly state when to use this tool versus alternatives. No exclusions or when-not-to-use guidance is given, leaving the agent to infer usage from purpose alone.

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