pve_realm_delete

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

No annotations provided, so description carries full burden. It clearly labels as MUTATION (HIGH, lockout-class), explains dry-run behavior, and mentions safety checks (counts users, refuses built-in). Could improve by detailing output format, but overall very transparent.

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, front-loaded with key action and critical warnings. No wasted words; every phrase adds value. Highly concise.

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 the high-stakes operation, description covers safety mechanisms (dry-run, refusal of built-in) and hints at the confirm parameter. Output schema exists for return values. Could mention common parameter proximo_target but it's documented in schema. Overall adequate for complexity.

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 (33%), and description adds value for 'confirm' parameter by indicating its role in proceeding with deletion. However, 'realm' parameter lacks additional context beyond its name. Proximo_target is documented in schema. Adds some meaning but not fully compensating for low 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?

Clearly states 'delete an auth realm' with specific verb and resource. Distinguishes from siblings like pve_realm_create, pve_realm_get, pve_realms_list by specifying it's a deletion operation. Also notes refusal of built-in realms, which adds clarity.

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 dry-run by default and that confirm=True is needed for actual deletion. Also states it refuses built-in pam/pve realms, providing clear exclusion criteria. The description gives guidance on when to use (to delete a realm) and when not to (for built-in realms).

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