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

Annotations already establish read-only, idempotent, non-destructive, non-open-world behavior, so the description is not responsible for the safety profile. It adds useful context beyond annotations: the reverse-chronological order, what each ledger entry represents, how to page, and the owner/admin restriction. It does not cover rate limits or return fields, but it meaningfully enriches the behavioral picture.

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 three sentences with no wasted words, front-loading the core purpose before pagination and permission details. Every sentence earns its place by adding distinct information.

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?

There is no output schema, so the description bears some burden for explaining return content, and it does so by naming entry types and ordering. It covers pagination and access requirements but does not describe the fields within each entry (amount, timestamp, etc.), leaving a small gap for a ledger tool. Overall it is complete enough for correct invocation.

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 description coverage is 100%, so the schema already documents both parameters fully. The description reinforces cursor usage ('Pass nextCursor back as cursor for the next page') and implies newest-first ordering, but adds no syntax or meaning beyond what the schema provides. The baseline of 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource: 'List where the workspace's credits went.' It further distinguishes itself from siblings like get_billing by specifying a paginated ledger with one entry per mission, grant, adjustment, and expiry. An agent can tell exactly what this tool returns and how it differs from a billing summary.

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 gives clear usage context: newest-first ordering, entry composition, pagination via nextCursor, and an explicit permissions restriction ('Owners and admins only'). It does not name alternative tools or state when not to use this one, but the operating context is unambiguous.

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