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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds the account-connection/auth prerequisite and the shape of the returned data, but says nothing about freshness, caching, or failure modes when the account is not connected.

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?

A single front-loaded sentence that leads with the scope qualifier ('For a company that uses the TrimCarbon offset API') before enumerating outputs. It is slightly dense but every clause earns its place; no redundant filler.

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 an output schema exists, the description need not detail return values, and it still gives a useful summary plus the connectivity prerequisite. The only omission is how this differs from get_my_impact, which an agent could reasonably confuse it with.

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 the baseline is 4 — there is no argument syntax an agent needs documented, and the schema is trivially complete at 100% coverage.

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 a specific verb+resource (API CO₂ offset impact) and enumerates the exact breakdown returned: total, last 30 days, by month, plus API access status. The 'TrimCarbon offset API' scope implicitly separates it from the broader get_my_impact and list_my_offsets, but it never explicitly routes the agent away from those siblings.

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?

It states a precondition — the company must use the TrimCarbon offset API and the user must connect their TrimCarbon account — which is genuine usage context. However, it gives no when-to-use vs. when-not guidance and never mentions the closely related get_my_impact or list_my_offsets, leaving the agent to infer selection.

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