pve_update_ha_group

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Update HA group', which implies a mutation operation but fails to describe effects like whether changes are destructive, require specific permissions, or have side effects. This leaves critical behavioral aspects undocumented.

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 with just two words, 'Update HA group', and is front-loaded with no unnecessary information. While it lacks detail, it is not verbose or poorly structured, earning full marks for conciseness.

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 of updating an HA group (a mutation operation with 5 parameters) and the absence of annotations and output schema, the description is incomplete. It does not explain what an HA group is, the impact of updates, or return values, leaving significant gaps for the agent to understand the tool's context and behavior.

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?

The schema description coverage is 100%, with all 5 parameters clearly documented in the schema. The description adds no additional meaning about parameters, such as usage examples or constraints beyond the schema. This meets the baseline score of 3, as the schema adequately covers parameter semantics.

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 'Update HA group' is a tautology that restates the tool name without adding meaningful context. It specifies the verb 'update' and resource 'HA group', but provides no information about what aspects are updated or what an HA group is, making it vague and minimally helpful beyond the name.

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 offers no guidance on when to use this tool versus alternatives. It does not mention sibling tools like 'pve_create_ha_group' or 'pve_get_ha_group', nor does it provide any context, prerequisites, or exclusions for usage, leaving the agent with no direction.

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