offsets__verra_retirement_record

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

The description declares the tool is read-only, which is a key behavioral trait. It also explains the current and future state (portal vs. API) and lists the data elements generated. Without annotations, this provides adequate transparency, though output format is not fully detailed.

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 a single dense paragraph containing valuable information but lacks structure. It could be more concise and better organized (e.g., separate purpose, usage, behavioral notes).

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 no output schema, the description lists generated fields but omits output format. It explains the workflow role but does not cover parameter meanings. For a tool with zero schema description coverage, more detail is needed to be fully complete.

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 0% (no parameter descriptions in schema). The description does not explain what purchase_id or retirement_reason are or how they affect the output. The agent must infer from context, which is insufficient.

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 generates Verra-portal-ready retirement records for Verra supply, listing specific data elements (project id, serial, vintage, etc.). It differentiates from sibling tools like offsets__verify_retirement and offsets__list_credit by focusing on record generation for a specific registry.

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 implies usage in a workflow (generate then submit under Viridis account) but does not explicitly state when to use this tool over alternatives or when not to use it. No exclusions or comparisons to siblings.

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