pve_node_storage_backend_delete

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

No annotations provided, so description carries full burden. It explicitly declares mutation, high risk, no undo, and details backend-specific effects. Also notes that the endpoint is not live-verified. Missing auth/rate limits but sufficient for a destructive action.

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?

Front-loaded with verb and resource, then risk, then details. Concise sentences, no fluff. The structure is logical, though the smoke-confirmation note could be placed more naturally.

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?

Covers purpose, usage, behavioral details, and confirmation requirement. Has output schema so return values not needed. Missing error conditions or prerequisites, but adequate for a delete operation.

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 low (17%). The description adds meaning by explaining confirm=True for execution and backend-specific impacts, but does not clarify name, node, cleanup parameters. Partially compensates but not fully.

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 'destroy a storage backend on the node' with specific verb and resource. It distinguishes itself from sibling tools like pve_node_storage_backend_create and pve_node_storage_backend_list by explicitly being the delete operation.

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?

Provides clear context: it's a high-risk, irreversible mutation. Mentions backend-specific consequences and that confirm=True is required to execute. However, lacks explicit when-not-to-use or alternatives (e.g., pve_storage_delete for different storage types).

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