vm_health_rca

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

No annotations given, so the description carries the burden. It explicitly labels as [READ] indicating read-only operation, and lists the types of findings, providing a good overview of expected behavior without side effects.

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?

Well-structured with a header, bullet list of checks, and argument descriptions. Slightly verbose in the bullet list but overall efficient and clear.

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 2 parameters, no output schema, and no annotations, the description covers purpose, parameters, and the nature of output (cause+action per finding). Sufficient for a simple 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?

Schema coverage is 0%, but the description fully explains both parameters: vm_id (optional, for single VM analysis) and target (optional, default). Adds significant meaning beyond the schema.

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 clearly states it performs root-cause analysis on VM health, listing specific flags (halted, paused, missing guest tools, CPU/memory pressure). This distinguishes it from sibling tools like backup_failure_rca or sr_usage_rca.

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?

Provides clear context: analyze one VM with vm_id or the whole fleet. Implicitly guides when to use this tool for VM health issues, but does not explicitly exclude other tools or scenarios.

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