pve_realm_delete

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

With no annotations, the description fully explains behavior: dry-run preview, reads users to count lockouts, refuses built-in realms (permanent, no undo), synchronous, returns dict. Discloses key safety aspects. No mention of permissions or rate limits, but core behaviors 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?

Description is concise (two sentences with added details), front-loaded with danger warning (MUTATION, lockout-class), and uses formatting for emphasis. Every sentence adds value.

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 output schema exists, description explains return types (PLAN for dry-run, dict for execution). Mentions synchronous, no UPID. Covers key aspects for safe use (dry-run, built-in refusal, user counting). Missing info about permission requirements, but not critical 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 100%, baseline 3. Description adds meaning beyond schema: explains confirm parameter's role in dry-run vs execution, clarifies realm parameter's refusal of built-in realms, and describes proximo_target. Provides context not in 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?

Clearly states the tool deletes an auth realm, specifies it's a mutation (HIGH, lockout-class), and distinguishes from sibling tools like pve_realm_create, pve_realm_update, pve_realm_get, pve_realms_list. Also mentions refusal of built-in pam/pve.

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?

Provides explicit guidance: use pve_users_list to see who authenticates through the realm first, dry-run by default, confirm=True to execute. Implicitly warns against using for built-in realms. Could be more explicit about when not to use, but adequate.

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