pve_pool_delete

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

Discloses mutation behavior, dry-run default, synchronous execution, return value (null), and side effect (orphaned ACLs). No annotations are provided, but the description fully covers behavioral traits.

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?

Concise, front-loaded with purpose, no unnecessary words. Every sentence adds value.

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?

Fully covers preconditions, execution modes, side effects, return value, and references related tools. Output schema exists but description already explains return null.

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?

Despite 100% schema coverage, the description adds meaningful context: that poolid must refer to an existing empty pool, that confirm controls dry-run vs execution, and the reference to pve_pool_update for emptying. This goes beyond the schema.

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?

Clearly states 'delete a resource pool' with the MUTATION prefix. Distinguishes itself from sibling tools like pve_pool_create, pve_pool_get, pve_pools_list, and pve_pool_update by 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 explicit when-to-use guidance: preconditions (pool must be empty, empty it with pve_pool_update), dry-run by default, how to execute (confirm=True), and synchronous behavior. Clearly differentiates from pve_pool_update for emptying.

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