VPS_restoreBackupV1

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

With no annotations, the description carries full burden. It explicitly warns 'All data on the virtual machine will be overwritten' (destructive hint) and mentions the process may take time. This is comprehensive for a restore operation.

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 compact (3 sentences in 2 paragraphs) with key info upfront. The bold warning is effective. Could be slightly more concise, but no fluff.

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?

No output schema exists, and the description doesn't mention what the response contains (e.g., action ID for tracking). Given the asynchronous nature, omitting this reduces completeness. Sibling tool VPS_getActionDetailsV1 exists, but not referenced.

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 coverage is 100% with basic descriptions ('Virtual Machine ID', 'Backup ID'). The description doesn't add extra meaning beyond what the schema already provides, so baseline score applies.

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 backup for a specified VM. It distinguishes from VPS_restoreSnapshotV1 by focusing on backup vs snapshot. The bold warning about data overwrite clarifies the impact.

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 last sentence 'Use this endpoint to recover VPS data from backup points' gives usage context. However, it doesn't explicitly contrast with restoreSnapshot or specify when not to use (e.g., if data preservation is needed).

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