pve_group_delete

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is a high-risk mutation, dry-run by default, warns about orphaned ACLs, is permanent with no undo, synchronous, and returns a dict. It does not mention permission requirements or error handling, but the key behavioral traits are covered.

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 three sentences long, tightly packed with essential information. It front-loads the action and key behavior ('MUTATION (HIGH): delete a group. Dry-run by default...') and then explains execution and a pre-check recommendation. Every sentence earns its place with 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?

For a simple 3-parameter mutation tool, the description covers the core workflow (dry-run, confirm, synchronous, pre-check). With an output schema present, the description does not need to detail return values. A minor gap is not mentioning error scenarios like non-existent groups, but overall it is comprehensive enough for an AI agent to use correctly.

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%, so the baseline is 3. The description adds minimal value beyond the schema: for 'confirm' it reiterates the dry-run/execute behavior already in the schema description, and for 'groupid' and 'proximo_target' it does not add new information. The description is mostly redundant regarding parameters.

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 starts with 'MUTATION (HIGH): delete a group', which is a specific verb and resource. It clearly states the action and distinguishes from sibling tools like pve_group_update (modify) and pve_group_create (add) by focusing on deletion. The dry-run and confirm behaviors are also introduced.

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 advises using pve_group_get first to see current members before deletion, and explains that dry-run is default while confirm=True executes the mutation. It provides a clear usage pattern but does not explicitly state when not to use this tool or compare to alternatives like pve_group_update for removing members.

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