pve_user_delete

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

Discloses mutation, dry-run default, PLAN functionality, permanence, admin lockout risk, synchronous behavior. With no annotations, description carries full burden; it covers most key behaviors but could elaborate on exact side effects of execution (e.g., token invalidation).

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?

Two sentences, efficiently front-loaded with type and risk. Every clause adds value; no redundancy or fluff.

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?

Despite complexity of permanent delete with dry-run, description covers essential aspects. Output schema exists (not shown) so return details are not required. Adequate for an 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 parameters are well-documented there. Description adds context linking confirm param to dry-run vs execution, but does not add new syntax or constraints beyond schema.

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 clearly states 'delete a user' with verb and resource. Distinguishes from sibling pve_user_update by contrasting disable vs delete. Also mentions dry-run default behavior.

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 says when to use (permanent delete) and when not (disable login -> use pve_user_update). Highlights admin lockout risk and dry-run preview for safe evaluation.

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