pve_group_delete

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

Discloses mutation (high), dry-run behavior, reading members, and warning about orphaned ACLs. No annotations provided, so description carries full burden. Missing details on reversibility or additional side effects, but sufficient.

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?

Single sentence, front-loaded with key info, no wasted words. Efficiently communicates core functionality and safety behavior.

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?

Has output schema, so return values not needed. Lacks prerequisites (e.g., group existence) and error conditions. Mentions plan and ACL warnings, but could be more complete about what the plan outputs. Adequate for a deletion tool.

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 33% (only proximo_target has description). Description mentions confirm=True but does not explain groupid or confirm parameter meanings beyond implication. Does not compensate sufficiently for low schema 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?

Explicitly states 'delete a group' with verb and resource. Distinguishes from sibling tools (create, get, list, update) and mentions dry-run behavior. Very clear.

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?

Describes dry-run by default and confirm=True to actually delete. Warns about orphaned ACLs, guiding safe usage. Could be more explicit about when to use confirm=True vs confirm=False, but overall clear.

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