pve_delete_storage_content

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive operation, the description doesn't specify whether this action is reversible, what permissions are required, if it affects running systems, or what happens to associated data. For a destructive tool with zero annotation coverage, this is a significant gap in safety and operational context.

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 extremely concise at four words, with zero wasted language. It front-loads the key action ('Delete') and target ('storage content (volume)'), making it easy to scan. However, it might be overly terse given the tool's destructive nature and lack of supporting context in other fields.

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 annotations and no output schema, the description is incomplete. It doesn't address critical context like irreversible deletion, permissions, impact on virtual machines using the volume, or error handling. The high schema coverage helps with parameters, but overall, the description fails to provide sufficient guidance for safe and correct usage in a complex system like Proxmox.

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%, with clear descriptions for node, storage, and volume parameters. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or interdependencies. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, though the description could have added value by explaining the hierarchical relationship between these parameters.

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 'Delete storage content (volume)' clearly states the action (delete) and target (storage content/volume), which is specific enough to understand the basic function. However, it doesn't differentiate this tool from similar deletion tools like pve_delete_storage or pve_delete_container, which also remove resources in the Proxmox environment. The description is adequate but lacks sibling differentiation.

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 no guidance on when to use this tool versus alternatives. There are many deletion tools in the sibling list (e.g., pve_delete_storage, pve_delete_vm, pve_delete_container), but the description doesn't explain that this specifically deletes volumes within storage, not the storage itself or other resources. No prerequisites, warnings, or context for usage are mentioned.

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