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

With no annotations provided, the description carries the behavioral disclosure burden. It usefully discloses that the data is public, scoped to corrections on published pieces, and returned in original ledger order. However, it does not mention pagination, response format, or explicitly confirm there are no side effects, though 'ledger' and 'list' weakly imply read-only behavior.

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, well-structured sentence. It front-loads the core identity ('public corrections ledger') and then efficiently lists the content and ordering. Every phrase earns its place with no redundancy.

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 zero-parameter, read-only list tool, the description is nearly complete: it defines scope, content, ordering, and public accessibility. Without an output schema, it could be more explicit about the exact returned fields, but 'what was wrong, what changed, and when' gives a solid expectation.

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 has zero parameters, and the schema confirms this with an empty properties object. The description provides all necessary semantic context; there are no parameter expectations to clarify. The baseline for zero-parameter tools is 4.

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 identifies the tool as a corrections ledger listing logged errors on published pieces, including what was wrong, what changed, and when. It is easily distinguishable from sibling tools like get_audit or list_letters because it specifically targets corrections entries, though it does not explicitly name a sibling alternative.

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 when to use it: whenever an agent needs the public record of corrections for published pieces. It does not explicitly state when not to use it or compare it to related tools such as get_audit or get_claim_ledger, leaving some routing inference to the agent.

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