pve_storage_delete

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

No annotations exist, so description carries full burden. It discloses mutation with HIGH severity, dry-run behavior, PLAN output warnings, data not erased, confirm=True execution, null return, and undo limitations.

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?

Two sentences with no wasted words: first sentence states purpose and dry-run, second sentence covers confirm and undo. Front-loaded with key information.

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?

Given the output schema exists, description need not explain return values, yet it mentions typical null. Covers all essential aspects: mutation nature, dry-run, confirm, undo, and side effects.

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 100%, but description adds significant meaning: confirms default false means dry-run, explains storage parameter as ID, clarifies confirm=True executes, and notes typical null return.

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, distinguishes it from pve_storage_create (re-add) and pve_storage_update, and specifies the verb 'remove' with a clear resource scope.

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?

Explicitly describes dry-run default behavior, warns about inaccessibility of guest disks/backups, and mentions no undo except re-adding via pve_storage_create, providing 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.