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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, but the description adds genuinely useful context: the deletion is permanent and includes history, which qualifies the blast radius. It still omits whether owner permission is required, whether collaborators lose access, and whether the operation can be undone by any means.

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?

One front-loaded sentence with zero filler; the permanent/irreversible nature is stated immediately. Nothing in it is wasted.

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 tool is simple (one optional parameter, output schema present, rich annotations), and the description covers the core action and its permanence. For an irreversible destructive operation, however, it should at least note permission requirements or the effect on collaborators and existing entries.

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 a single well-documented parameter (owner/name format, defaults to the credential's ledger restriction), so the schema carries the semantics. The description adds nothing about the ledger identifier, leaving the baseline 3.

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?

Names a specific verb (permanently delete) and resource (a ledger) plus the scope of the deletion ('including its history'). It is clear on its own, but it never distinguishes itself from sibling leaveLedger, which an agent could easily confuse with deleting a ledger, so it falls short of a 5.

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?

There is no statement of when to use this versus leaveLedger, updateLedger, or deleteLedgerFiles, and no prerequisites such as required ownership or confirmation. The agent must infer usage entirely from the tool name and annotations.

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