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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description correctly indicates an append-only, read-only nature. It adds context by mentioning 'append-only' and the optional balance snapshot, which is beyond the annotations. No contradiction.

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 sentence with structured event names and the endpoint in parentheses. It is concise and front-loads the core concept (append-only ledger events) before listing specifics. No fluff, but could be slightly more explicit about the action.

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, no-parameter tool, the description provides a solid list of event types and confirms the append-only nature. However, it doesn't describe the output format (e.g., fields like timestamp, amount, type) or how pagination works, which could be useful. Given the output schema is absent, complete guidance is missing, but the tool is simple enough that this is acceptable.

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 100% with zero parameters, and the description mentions caller_id and the available event types, providing context that is not visible from the empty schema. Since there are no parameters to document, the baseline is 4, and the description effectively fills the gap.

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 specific event types (credit.grant, credit.purchase, etc.) and the endpoint, but it doesn't clearly state the primary action ('retrieve' or 'list'). It lists what the events are, but the verb is implicit from the endpoint, which may not be immediately obvious to an agent.

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 hints at events for this caller_id but doesn't explain when to use this tool versus credit_balance or other credit-related siblings. It lacks explicit conditions or alternatives, leaving the agent to infer that this is for listing events rather than checking current balance.

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