pve_firewall_ipset_delete

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

With no annotations, the description carries full burden and effectively discloses key behaviors: dry-run by default, plan output, force semantics, and precondition (refuse if rule references). However, side effects beyond deletion are not mentioned.

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?

The description is brief and front-loads the purpose with 'MUTATION: delete an IP set'. The additional details are concise but the 'MUTATION:' prefix adds no value. Overall efficient but could be slightly more structured.

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 8 parameters and an output schema, the description covers core purpose and important behaviors but omits explanations for parameters like kind, node, vmid, scope, and confirm. It is adequate but leaves significant gaps for a tool with many parameters.

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 (13%), and the description only adds meaning for the 'force' parameter ('force=True wipes all members'). Other parameters like name, node, vmid, scope, confirm are not explained, failing to compensate for the coverage gap.

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 the tool deletes an IP set, with the verb 'delete' and the resource 'IP set'. It distinguishes itself from sibling tools like pve_firewall_ipset_create or pve_firewall_ipset_entry_remove by being the only delete operation for ipsets.

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?

The description mentions dry-run behavior and constraints (force=True wipes all members, PVE refuses if rule references set), but does not explicitly compare to alternatives like pve_firewall_ipset_entry_remove for removing individual entries. Usage guidance is implied but not comprehensive.

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