pve_storage_delete

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

No annotations provided, so the description fully covers the mutation's high risk, dry-run behavior, cluster-wide scope, and the consequence that guest disks/backups become inaccessible (not erased). No contradictions found.

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?

A single, well-structured sentence that front-loads the mutation risk and clearly explains the dry-run mechanism and confirm flag. No wasted words.

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 high-mutation tool, the description covers all essential aspects: action, scope, dry-run, consequences, and the confirm parameter. The presence of an output schema further reduces the need to explain return values.

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 coverage is low (33%), but the description adds critical context: confirm=True enables actual deletion (vs. dry-run). Storage parameter is self-explanatory, and proximo_target has its own schema description.

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 it removes a storage definition cluster-wide, with specific mention of dry-run behavior and warning about guest disks/backups becoming inaccessible. This distinguishes it from other storage tools like pve_storage_create or pve_storage_content_delete.

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 explains the dry-run default and the need for confirm=True to execute, but does not explicitly contrast with sibling tools like pve_storage_content_delete or pve_storage_update.

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