reset_vm

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

With no annotations provided, the description fully discloses key behavioral traits: it is destructive, causes immediate restart without graceful shutdown, may cause data loss, and requires confirm=true to execute (returns a preview otherwise). This exceeds basic expectations and provides critical 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 exceptionally concise and well-structured. It opens with a strong 'DESTRUCTIVE' warning and the core action, followed by two clarifying sentences and a clean Args list. Every sentence contributes meaningful information with no redundancy.

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 two-parameter destructive action, the description covers the operation, consequences, and confirmation mechanism. An output schema exists, so return values need not be described. This is a complete and self-sufficient description for the tool's complexity.

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 has 0% description coverage, so the Args section is necessary. It adds value by explaining the confirm parameter's behavior ('Must be true to execute. Returns a preview otherwise'), which is not evident from the schema alone. vm_id's description is minimal but sufficient for its purpose.

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 the tool's action: 'Reset (hard restart) a virtual machine' and equates it to 'pressing the reset button.' It explicitly distinguishes from graceful shutdown by noting 'without graceful shutdown,' separating it from sibling tools like shutdown_vm.

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?

While no explicit alternatives are named, the description implies usage context through 'hard restart,' 'without graceful shutdown,' and the 'DESTRUCTIVE' warning. This signals when to use this tool (forced immediate reset) versus more graceful options, though exclusions are not explicitly stated.

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