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

The destructiveHint annotation already marks the tool as destructive, and the description adds meaningful context beyond it: the deletion is permanent and requires explicit user confirmation. This gives an agent important behavioral information about irreversibility and the need for a confirmation step.

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 two short sentences with zero wasted words. The primary action and permanence are front-loaded, and the confirmation requirement is stated immediately after.

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 simple destructive operation with three well-documented parameters and the destructiveHint annotation, the description is largely complete. It states the resource, permanence, and confirmation prerequisite; a fully complete description might also note that the deletion cannot be undone, but 'Permanently' already implies this.

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%, and each parameter already has a clear description, especially `confirm`, which states it must be true and only set after explicit user confirmation. The tool description itself adds no additional parameter-level meaning beyond what the schema already provides.

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 ('delete'), a specific resource ('vendor credit'), and a clear scope ('from QuickBooks Online'). The word 'Permanently' adds an important precision that distinguishes this destructive action from a void or reversible operation.

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 provides a clear, explicit prerequisite: this should only be invoked after the user has explicitly confirmed the deletion. It does not enumerate alternatives or exclusions, but the resource-specific naming and confirmation gate make the intended usage clear.

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