pve_create_ha_group

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create HA group' implies a write/mutation operation but doesn't disclose any behavioral traits: no mention of permissions required, whether this affects running services, what happens on failure, or what the expected outcome is. The description is minimal and fails to provide necessary operational context.

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 just two words, with no wasted language. However, this brevity comes at the cost of being under-specified rather than efficiently informative. It's front-loaded but lacks the substance needed for proper tool understanding.

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?

For a creation tool with 5 parameters, no annotations, and no output schema, the description is severely incomplete. It doesn't explain what HA groups are, when they're used, what the creation process entails, or what happens after creation. The agent would need to infer everything from the parameter names and schema alone.

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%, with all 5 parameters well-documented in the schema itself. The description adds no parameter information beyond what's already in the structured schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 'Create HA group' is a tautology that restates the tool name without adding meaningful context. It specifies the verb 'Create' and resource 'HA group', but doesn't explain what an HA group is or what creation entails. Compared to siblings like pve_create_container or pve_create_vm, it lacks differentiation beyond the resource type.

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 provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when HA groups are needed, or how this relates to other HA tools like pve_create_ha_resource or pve_list_ha_groups. The agent receives zero contextual usage information.

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