Restore snapshot

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

Annotations already indicate destructiveHint=true, so the destructive nature is captured structurally. The description adds that restoring reverts the VM to a previous state, which implies overwriting current state, but it does not warn about data loss, VM downtime, or irreversibility beyond the annotation.

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 short and front-loaded with the core action in the first sentence. The later sentences add context but are somewhat repetitive with the opening, so not every sentence fully earns its place.

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 destructive operation, the description lacks critical operational details: it does not clarify which snapshot is restored when no snapshot identifier parameter is provided, nor does it mention effects on the running VM. The description is not complete enough for an agent to fully understand the consequences of invoking this tool.

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 parameter 'virtualMachineId' is already documented. The description adds no extra meaning about how the target snapshot is selected, which is notable because no snapshot identifier parameter exists.

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: restore a specified virtual machine to a previous state using a snapshot. It distinguishes this from backup-related tools by using 'snapshot' terminology, though it does not explicitly contrast with VPS_restoreBackupV1.

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 gives clear use cases: system recovery, undoing changes, and testing. It tells the agent when this endpoint is appropriate, though it does not mention exclusions or alternative tools.

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