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

Annotations already mark this as destructive and non-read-only, and the description consistently reinforces this with 'permanently delete' and 'requires explicit user confirmation.' It adds context beyond the annotations by emphasizing irreversibility and the need for consent, though it does not detail cascade effects or recovery limitations.

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?

Two short sentences with no filler. The core action and the critical confirmation requirement are front-loaded, and every sentence adds value.

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 destructive tool with no output schema, the description provides the essential behavioral facts: permanent deletion, target system, and user-confirmation requirement. It could mention side effects or prerequisites for deletion, but the annotations plus description cover the main safety-critical context.

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 parameters (id, company, confirm) are already fully documented. The description adds no new parameter-level meaning beyond restating the confirmation requirement already present in the confirm field.

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'), resource ('credit memo'), and system ('QuickBooks Online'), clearly distinguishing it from sibling delete_* tools like delete_invoice or delete_vendor_credit. The word 'permanently' adds important scope beyond the title.

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?

No guidance is given about when to choose this tool versus alternatives such as voiding, updating, or searching credit memos. The only condition mentioned is explicit user confirmation, which is a prerequisite rather than a usage-vs-alternative guideline.

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