enable_vm_ha

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

No annotations exist, and the description discloses no behavioral traits. It does not state that this modifies VM configuration, requires cluster resources, or has reversible effects. The description is silent on permissions and side effects, leaving the agent with no safety information.

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 only eight words, which is efficient in length, but it essentially restates the tool name and provides no explanatory value. It is under-specification rather than genuine conciseness, as it fails to include any information beyond what the name already implies.

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?

With 6 parameters, no annotations, and no output schema, the description should explain the effect, potentially note the 'group' and 'state' parameters, and give usage guidance. Instead, it offers only the bare phrase, making it inadequate for an agent to invoke correctly.

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 input schema already documents all 6 parameters with descriptions, yielding 100% coverage. The description adds no parameter-level detail, so it relies entirely on the schema. Baseline of 3 is appropriate given full 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?

The description 'Enable High Availability for a VM' is nearly a verbatim expansion of the tool name 'enable_vm_ha', providing no additional specificity beyond what the name already conveys. It identifies the resource (VM) and action (enable HA), but this is a restatement rather than a clarifying definition.

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 usage context is provided. The description does not indicate prerequisites, situations to use this tool over enable_container_ha, or any warnings. There is no guidance on when to use or 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.