offsets__settlement_batch

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

No annotations exist; the description indicates it is read-only and returns specific fields, but lacks details on authentication, rate limits, or error scenarios.

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 sentence that communicates core information efficiently, though it could be slightly restructured for improved readability.

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?

For a read-only tool with 2 parameters and no output schema, the description covers essential aspects—purpose, returned fields, and optional filter—missing only potential edge cases or performance considerations.

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%, so the description compensates by explaining the 'buyer' parameter context and describing 'since' as an optional ISO-8601 timestamp, adding meaning beyond the plain schema.

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 it is a read-only cash-settlement summary for a buyer, listing exact sums of retirements with optional timestamp filtering. It uses specific verbs and resources, distinguishing it from sibling tools like offsets__get_purchase or offsets__list_credit.

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 for settlement purposes ('the statement a human settles in one transfer') but does not explicitly state when to use this tool versus alternatives or provide exclusions.

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