create_vm_snapshot

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

Annotations already provide basic behavioral hints (non-read-only, non-destructive, non-idempotent). The description adds one requirement (risk level) but does not elaborate on additional behaviors such as whether the VM must be running, what happens if snapshot name exists, or side effects like disk I/O. With annotations present, the description adds marginal value.

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 extremely concise (one sentence plus a requirement) and front-loaded with the purpose. It is not verbose, but could be slightly more informative without losing conciseness, hence a 4.

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?

The description lacks important context such as prerequisites (beyond risk level), constraints (unique snapshot name, VM existence), and potential side effects. An output schema exists, so return values are covered, but the overall contextual information for correct invocation is insufficient.

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 100% description coverage, so the schema already documents each parameter. The description does not add any parameter-specific meaning beyond what is in the schema, earning the baseline score of 3.

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 specific action 'Create a snapshot of a VM' with a verb and resource. It distinguishes from sibling tools like delete_vm_snapshot or create_container_snapshot by specifying the target (VM vs container) and action (create vs delete).

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?

The description states a prerequisite (PROXMOX_RISK_LEVEL=lifecycle) but provides no explicit guidance on when to use this tool vs alternatives like create_container_snapshot or rollback_vm_snapshot. Usage context is implied through the tool name and description but not detailed.

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