vm_reset

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

Discloses that the tool destroys the current VM AND deletes its saved snapshot, making the destructive nature fully transparent. No annotations were provided, so the description carries the full burden and meets it thoroughly.

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?

Two short sentences front-loaded with the action and effects. No extraneous words, every sentence adds value.

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 simple tool with one parameter and no output schema, the description adequately covers purpose, side effects, and post-condition. Includes needed context without over-explaining.

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?

Only one parameter 'id' with schema description 'Sandbox id to reset'. Schema coverage is 100%, so baseline is 3. Description adds no extra information 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?

Clearly states the verb 'Reset', the resource 'VM', and specifies 'to a clean state'. Distinguishes from sibling tools like vm_destroy (which only destroys) and vm_create (which creates) by describing the combined destruction of VM and snapshot.

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?

Implicitly conveys when to use: to get a clean state from the base image. Mentions the effect on subsequent vm_create, providing context. Does not explicitly contrast with alternatives like manual destroy+snapshot delete, but the intent is clear.

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