pve_mapping_usb_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, describes dry-run behavior, and discloses consequence for VMs. Lacks details on reversibility or auth requirements, but adds significant behavioral context.

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 concise sentences, front-loaded with action and type. No wasted words, essential information presented efficiently.

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 core action, dry-run, confirm flag, and consequence. Output schema exists, so return values are covered. Missing edge cases (non-existent mapping) but adequate for typical use.

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%). Description adds meaning for confirm (dry-run, execute) but does not elaborate on mapping_id or proximo_target. Baseline 3 is appropriate as description partially compensates for low coverage.

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 it deletes a USB cluster mapping, with 'MUTATION:' prefix indicating write operation. Distinguishes from sibling tools (create, list, update) by explicitly naming the action.

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 mentions dry-run default and need for confirm=True to execute, providing clear usage steps. Warns about VMs losing USB device path, aiding agent decision. However, no explicit when-not-to-use or alternatives mentioned.

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