create_snapshot

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

With no annotations, the description carries the behavioral burden. It discloses the 'DESTRUCTIVE' nature (though arguably misleading for a snapshot creation), the confirmation requirement with a preview mode, and that memory is captured only if the VM is running. This provides meaningful behavioral context beyond the bare schema.

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 concise and front-loaded with the action. It uses a clear 'DESTRUCTIVE:' prefix and lists args in a structured format. However, the prefix may be unnecessary and the args section could be formatted as a list for better scannability, but overall it is efficient and not verbose.

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 moderately complex tool with no annotations and an output schema (not shown), the description covers the essential behavior: what is captured, how confirm works, and the optional name. It does not explain failure conditions or permissions, but for a snapshot creation tool, the description is sufficiently comprehensive for an agent to invoke it 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?

Schema description coverage is 0%, so the description must compensate. It explicitly explains all three parameters: vm_id ('The VM identifier'), name ('Optional name for the snapshot'), and confirm ('Must be true to execute. Returns a preview otherwise'). This adds clarity beyond the schema's type/default fields, though vm_id could be more specific.

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 action: 'Create a snapshot of a virtual machine' and elaborates on what is captured (memory if running and disks). This distinguishes it from sibling tools like list_snapshots, revert_snapshot, and delete_snapshot by specifying the create operation.

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 explicit guidance is given on when to use this tool versus alternatives. The description mentions that confirm must be true to execute and otherwise returns a preview, which is parameter-level guidance but not tool-selection guidance. There is no mention of prerequisites, typical use cases, or when not to use this tool.

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