list_ha_groups

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

With no annotations, the description adds some context by defining HA groups, but it does not disclose behavioral traits like pagination, ordering, or performance. Minimal behavioral disclosure beyond the core operation.

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?

Single sentence, front-loaded with the action 'List HA groups', no wasted words. Every part earns its place.

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 simple list tool with no parameters and output schema present, the description fully explains the purpose. It is complete for an agent to understand when to invoke this tool.

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?

No parameters exist, and schema coverage is 100% (empty). The description adds value by explaining the meaning of HA groups, which is beyond the schema. Baseline 4 for 0 params is exceeded by the explanatory context.

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?

Description clearly states it lists HA groups and provides context that HA groups define which nodes can run HA resources. Verb and resource are specific, distinguishing it from siblings like list_ha_resources or create_ha_group.

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?

Description indicates when to use (list HA groups) but does not explicitly provide when-not-to-use or alternatives. It implies usage for viewing existing groups, but lacks explicit guidance.

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