Permanently Purge a Quarantined Item

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

Annotations already declare destructiveHint=true, but the description adds beyond that by stating the operation is irreversible and requires its own explicit human approval. This is valuable context for an agent deciding to invoke the tool.

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?

Exactly two sentences, front-loaded with the action ('Permanently delete'), no filler words. Every phrase earns its place: the target, the irreversibility, and the approval requirement.

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 description covers purpose and key behavioral caveats, but leaves the parameter semantics fully to the schema, and there is no output schema or return-value explanation. For a simple destructive operation this may be acceptable, but the lack of any parameter guidance and no description of the expected response/result makes it only minimally complete.

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 0%, and the description does not mention either parameter (quarantineRelativePath or rootIndex). It provides no additional meaning beyond the schema fields, which are self-descriptive but not explained. The description's reference to an 'item' vaguely implies the path parameter but does not compensate for the lack of schema documentation.

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 clearly states the action ('Permanently delete') and the target ('item that already lives in the quarantine directory'). It distinguishes this tool from siblings like whatbox_list_quarantine and whatbox_quarantine_path by specifying it's the irreversible second step.

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 clear context: it is the irreversible second step after quarantine and requires explicit human approval. This implies usage after whatbox_quarantine_path, though it doesn't explicitly name alternatives or say 'use when not to use'. The 'already lives in quarantine' condition adds a usage constraint.

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