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

Beyond the destructiveHint annotation, the description discloses the reach of the deletion ('with its cartons and packed lines'), the permanence implied by 'for good,' and the guard behavior for shipped lists. This is exactly the added behavioral context an agent needs before invoking a destructive operation.

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 three tight sentences with no filler. The core destructive effect is front-loaded, followed by the key exception and the safer alternative, so critical information is immediately visible.

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 two-parameter destructive tool with a rich destructiveHint annotation, the description covers the operation, its scope, its guard, and the alternative. Nothing an agent needs to decide whether and how to call this tool 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 the schema already fully documents both parameters: packing_list identifies the target and confirm must be true. The description does not add parameter-specific meaning, but it does not need to because the schema carries the load.

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 and resource: 'Delete a packing list for good, with its cartons and packed lines.' It also distinguishes the tool from cancellation by refusing shipped lists, so an agent can tell it apart from related packing-list tools.

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 explicitly says when deletion is inappropriate: a shipped list is refused because it is the shipment record. It also names the alternative path: 'Cancel a list you no longer want instead of deleting a real shipment,' giving clear when-to-use and when-not-to-use guidance.

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