pve_ha_groups_list

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

Despite no annotations, the description declares read-only, no state change, version-specific behavior, error handling details, and return format (list of group dicts with fields). Covers all behavioral aspects.

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 READ-ONLY, then version caveat, error behavior, and output format. Every sentence is informative with no 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?

Provides all necessary context: read-only, version dependency, alternative tool, error message, output structure. Given schema coverage and output schema presence, description is fully complete.

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?

Only one parameter (proximo_target) with 100% schema description coverage. The description adds no additional parameter semantics, but schema already explains its purpose. Baseline score of 3 is appropriate.

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?

Clearly states it lists all HA resource groups, specifies it is read-only, and distinguishes itself from the PVE 9 equivalent (pve_ha_rules_list). The description defines verb (list) and resource (HA resource groups) precisely.

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?

Explicitly states to use on PVE 8 and not on PVE 9, directing to pve_ha_rules_list as alternative. Clear when and when-not to use.

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