pve_ha_resource_remove

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

No annotations were provided, so the description fully covers behavioral traits. It discloses that it is a mutation, synchronous, dry-run by default, and that it does not stop the guest. It also describes the return value as typically null, not a UPID.

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 at three sentences, with the purpose front-loaded. Every sentence earns its place by providing critical information 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 is present, the description does not need to explain return values. It covers all necessary aspects: mutation, dry-run, execution, side effects, and alternative tool. It is complete for a tool with 4 parameters and 1 required.

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 100%, so baseline is 3. The description adds value by explaining the 'confirm' parameter's role (dry-run vs execution), but does not elaborate on other parameters beyond what the schema provides.

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 action: 'remove a guest from HA management'. It uses a specific verb and resource, and distinguishes from the sibling tool 'pve_ha_resource_add' by mentioning it as an alternative for re-adding HA management.

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 explicitly explains when to use this tool (to remove HA management) and the dry-run behavior. It also provides guidance on when to use the alternative tool 'pve_ha_resource_add' for re-adding management.

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