pve_role_delete

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

With no annotations provided, the description carries full burden. It labels the tool as 'MUTATION (HIGH)', explains the dry-run mechanism, that it reads ACLs to count broken grants, and that it refuses built-in roles. This is good behavioral disclosure.

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 extremely concise with two sentences and a parameter hint, front-loading key information (mutation label, purpose, dry-run behavior). Every sentence adds value without redundancy.

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 that an output schema exists (so return values are documented elsewhere), the description covers safety mechanisms and the confirm parameter. It could mention prerequisites or permissions, but overall it is fairly complete for a delete 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?

The schema has 33% description coverage (only proximo_target described). The description adds meaning to the confirm parameter by noting its role in confirming deletion, but adds little to roleid beyond what the schema provides. It partially compensates for low schema coverage but not fully.

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 'delete a role', which is a specific verb and resource. It distinguishes itself from sibling tools like pve_role_create, pve_role_update, and pve_roles_list by specifying the delete 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?

The description explains the dry-run default behavior and the need for confirm=True to execute deletion, and notes that built-in roles are refused. This provides clear context for safe usage, though it could explicitly state when not to use it (e.g., for built-in roles it already implies that).

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