pve_ha_resource_remove

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

With no annotations provided, the description fully covers behavioral traits: it labels the operation as 'MUTATION', describes dry-run and plan content, confirms the guest isn't stopped, and notes synchronous execution. No contradictions.

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?

Three sentences, front-loaded with risk label 'MUTATION', each sentence adds unique value (purpose, dry-run behavior, execution and sync nature). No wasted words.

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?

The description covers purpose, dry-run, execution flag, and sync—adequate for a mutation tool with an output schema. Missing details like prerequisite (guest must be in HA) or parameter 'kind' explanation, but overall informative.

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 only 25% (only proximo_target described). The description adds meaning for 'confirm' (dry-run vs execute) and implicitly for 'vmid' (the SID), but fails to describe 'kind' (default lxc) or 'proximo_target' beyond schema. This leaves significant gaps.

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 the tool removes a guest from HA management, using the verb 'remove' on a specific resource. It distinguishes from sibling tools like pve_ha_resource_add (add to HA) and pve_ha_resources_list (list), making its unique purpose evident.

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 behavior and how to execute with confirm=True, providing clear usage steps. It lacks explicit when-not-to-use or alternative tool mentions, but the context is sufficient for safe use.

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