pve_mapping_pci_delete

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

No annotations provided, so description carries full burden. Clearly labels as mutation, explains dry-run vs confirm, details side effects (VMs lose device path), and states irreversibility with no undo primitive. Covers all critical behavioral aspects.

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?

Three sentences, front-loaded with purpose. Each sentence adds value: mutation type, dry-run/confirm behavior, side effects, and recovery guidance. 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?

With output schema present, description explains return values for both confirm (status object) and dry-run (PLAN). Covers side effects, irreversibility, and recovery path. Complete for a mutation tool with dry-run capability.

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% with descriptions. Description adds value by explaining confirm's effect (dry-run vs execution) and default (false). It implicitly covers mapping_id. The proximo_target is well-described in schema. Adds context beyond schema for confirm.

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?

Description starts with 'MUTATION: delete a PCI cluster mapping', clearly specifying the action (delete) and resource (PCI cluster mapping). It distinguishes from sibling tools like pve_mapping_pci_create by mentioning re-creation as the undo mechanism.

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 the default dry-run behavior and how to execute with confirm=True. States consequences (VMs may fail to start) and recommends pve_mapping_pci_create for restoration. Lacks explicit when-not-to-use scenarios, but the delete context is clear.

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