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

Annotations already indicate destructiveHint=true and readOnlyHint=false, and the description adds that the deletion is permanent and requires explicit user confirmation. This is valuable behavioral context beyond the structured annotations, and there is no contradiction with destructiveHint.

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 no filler. The core action and target are front-loaded, and the confirmation requirement is stated immediately after, so an agent can parse the essential information quickly.

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 three-parameter destructive tool with fully documented parameters and a destructiveHint annotation, the description provides everything needed to select and invoke it: the action, resource, platform, permanence, and required user confirmation. Nothing an agent needs in order to call it correctly is missing.

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 id, company, and confirm are already fully explained in the schema. The tool description's mention of user confirmation mirrors the confirm parameter's schema description but adds no new parameter-level detail, so the baseline 3 is appropriate.

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 a specific verb, a concrete resource ('a purchase order'), and the platform ('QuickBooks Online'), so there is no ambiguity about the operation. The resource is named exactly as in the tool, which distinguishes it from sibling delete tools for other object types.

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?

It clearly implies when the tool is appropriate: when a purchase order must be permanently removed in QuickBooks Online. The explicit-confirmation requirement is a concrete precondition that tells the agent to gate the call on user approval. It does not explicitly contrast with alternatives, but the resource-specific name makes the primary alternative choice obvious.

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