create_ha_group

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

Explains parameter behaviors (e.g., nofailback, restricted) but does not disclose side effects, prerequisites (e.g., node existence), or return value. With no annotations, this is moderate coverage.

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?

Very concise, front-loaded with purpose, and structures parameters clearly. No extraneous information.

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?

Covers all parameters and hints at behavior, but misses prerequisites (e.g., nodes must exist, cluster setup) and does not mention idempotency or error conditions. Output schema exists but is not referenced.

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?

Provides detailed explanations for all parameters, including formatting examples (e.g., 'node1:2,node2:1') and semantic meanings. Compensates fully for the 0% schema coverage.

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 'Create an HA group' with a specific verb and resource. Distinguishes from siblings like create_ha_resource, but could provide a bit more context on what an HA group is.

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 explicit guidance on when to use this tool versus alternatives like create_ha_resource or update_ha_group. The description lacks usage context and prerequisites.

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