Restore VPS Snapshot

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

The annotation destructiveHint=true already signals destructiveness, but the description adds no additional context about what gets overwritten, whether the restore is reversible, or the impact on the current VPS state. It does not disclose any behavioral traits beyond what the annotation provides, so the description carries little extra 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 a single concise sentence with no filler or redundancy. It is appropriately sized for a tool with one parameter and a clear action.

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 tool is simple with one parameter and an annotation for destructiveness, but the description lacks any mention of side effects, return value, or operational requirements. While minimally adequate, it could be more complete by noting that the current VPS state is replaced or that an action is triggered.

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 covers 100% of the parameter 'vm_id' with a clear description, so the tool description does not need to add parameter details. Given the full schema coverage, a baseline score of 3 is appropriate; the description adds no semantic value 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?

The description 'Restore a VPS from snapshot' uses a specific verb and resource, clearly indicating the action and object. It distinguishes itself from sibling tools like vps_restore_backup and vps_create_snapshot by explicitly mentioning snapshot restoration for a VPS.

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?

There is no guidance on when to use this tool versus alternatives, such as vps_restore_backup or vps_create_snapshot. It does not mention prerequisites, conditions like VPS being stopped, or any scenarios where this tool is preferred.

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