proxmox_ha_resource

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

The description notes 'elevated' for create/update/delete actions, indicating privilege requirements. However, with no annotations, it lacks details on side effects, idempotency, or concurrency handling. It adds some value but leaves significant gaps.

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 concise, using a single sentence with pipe-separated actions. It is front-loaded with the core purpose. Could be improved with better structuring, but remains efficient.

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 complexity (11 parameters, multiple actions) and lack of output schema, the description is incomplete. It does not explain what HA resources are, how to use parameters together, or integrate with sibling tools like proxmox_ha_group. More context is needed.

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 high (91%), so the schema already explains most parameters. The description adds minimal value beyond listing action values, which are already in the schema. No extra meaning for other parameters.

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 starts with 'Manage HA resources' and lists specific actions (list, get, status, create, update, delete), clearly stating the tool's purpose. However, it does not explicitly differentiate from sibling tools like proxmox_ha_group, but the focus on HA resources is distinct.

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?

No guidance on when to use this tool versus alternatives such as proxmox_ha_group or proxmox_guest_*. The description does not provide context for selection, prerequisites, or exclusions.

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