offsets__book

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

The description indicates a read operation returning conservation totals, but without annotations it does not fully disclose behavior such as authentication requirements, data freshness, or potential side effects (if any).

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 short, but the bracketed prefix '[offsets — verified-credit carbon offset clearinghouse]' is redundant given the tool namespace. The core sentence is efficient and front-loaded.

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?

The description lacks details on output format, pagination, or interpretation of 'mass conservation totals'. With no output schema and no annotations, the agent has limited context to use the tool correctly.

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?

There are no parameters, so schema coverage is 100% and the description adds no additional meaning needed. Baseline score of 4 is appropriate.

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 defines the tool as returning 'the full credit book with per-credit and book-wide mass conservation totals', specifying the resource and the scope of data returned. It is distinct from sibling tools like offsets__list_credit and offsets__net_position.

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 alternatives such as offsets__list_credit or offsets__net_position. There is no mention of prerequisites or when not to use it.

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