offsets__verra_supply

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

The description includes 'Read-only' and describes the content (verified credits with provenance). However, without annotations, it does not disclose whether authentication is needed, rate limits, or caching behavior. The retirement split info is somewhat tangential.

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 concise (three sentences) and front-loaded with the core concept. The initial bracketed label '[offsets — ...]' is slightly redundant but does not significantly detract. Every sentence adds value, though the retirement split may be better placed elsewhere.

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 no parameters and no output schema, the description should detail the expected response. It mentions that credits have project id, serial, and vintage, but does not confirm the output structure (e.g., array, pagination). This is adequate but not 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?

No parameters exist, so the burden on the description is minimal. The schema coverage is 100% (empty), and the description appropriately avoids adding parameter details. Baseline score of 4 applies per the rules for 0 parameters.

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 identifies the tool as providing the tradeable Verra VCS book of verified credits with provenance details. It explicitly states 'Read-only,' which helps distinguish it as a query tool. However, it lacks an action verb like 'list' or 'get,' and the purpose is implied rather than directly stated.

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 guidance is provided on when to use this tool versus siblings such as 'offsets__list_credit' or 'offsets__verra_retirement_record'. The description does not mention alternatives, prerequisites, or context for use.

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