reset_vm

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

No annotations are provided, so the description bears the full behavioral burden, yet it only states that reset equals restart. For a VM reset it says nothing about whether this is a hard power-cycle, whether running workloads/in-flight state are lost, whether it is graceful or forced, or which permissions are required.

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?

A single four-word sentence with the verb front-loaded and zero filler. Nothing could be trimmed without losing the clarifying 'restart' synonym.

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?

For a disruptive restart operation with no annotations and no output schema, the description leaves out the operational essentials: data-loss risk, force vs graceful behavior, and any required state or permissions. The schema covers the parameter, but the description does not cover the tool's behavior.

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 description coverage is 100%, so the single 'vm' parameter (name or UUID) is already fully documented in the schema. The description adds no format or identification detail beyond what the schema supplies, which is the expected baseline when the schema does the work.

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?

States a specific verb (reset) with a clarifying synonym (restart) and the target resource (virtual machine), which is enough to distinguish it from siblings like start_vm or stop_vm at a glance. It stops short of explicitly contrasting reset with the stop/start pair or suspend/resume, so the boundary with those siblings is left implicit.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as stop_vm followed by start_vm. The agent must infer the selection criteria entirely from the tool name.

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