offsets__net_position

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

No annotations provided, so description must disclose behavior. It describes calculation logic but doesn't state if it's read-only, mutating state, or requires authorization. Side effects and data sources are unclear.

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?

Description is very short but includes a redundant prefix '[offsets — verified-credit carbon offset clearinghouse]'. It uses concise but jargon-dense language.

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?

Missing output schema and low schema coverage leave significant gaps. Description only mentions a flag 'carbon_accountable' without specifying the full output format or return behavior.

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%, and description does not explain the meaning of 'buyer' or 'emitted_g' (e.g., unit, format). Agent cannot determine what values to provide without domain knowledge.

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?

Description states the tool computes buyer's carbon position as emitted minus retired, and mentions a carbon_accountable flag. It distinguishes from siblings like offsets__buy_offset, offsets__book, etc., but uses jargon that may require domain knowledge.

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 explicit guidance on when to use this tool versus siblings. It doesn't state prerequisites or scenarios where it's applicable, nor does it mention alternatives.

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