Restore VPS Backup

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

The annotation destructiveHint=true already flags the operation as destructive. The description adds no additional context about the impact (e.g., overwriting current state, potential downtime, irreversibility). Since the description merely restates the action without enriching the safety profile, it adds minimal 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 only four words, which might seem concise, but it is under-specification rather than effective conciseness. It fails to provide necessary context and does not earn its place as a useful explanation, making it more of an omission than a well-structured description.

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 with no output schema, this description is severely incomplete. It does not explain what a backup restore entails, any prerequisites, potential side effects, or what the response might be. The tool would be hard to use safely without additional context.

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%, with clear descriptions for vm_id and backup_id. The description itself adds no parameter semantics, but according to the rubric, high schema coverage yields a baseline of 3. No extra meaning is provided, so the baseline stands.

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 backup.' is essentially a less specific restatement of the title 'Restore VPS Backup'. It does not distinguish this from sibling tools like vps_restore_snapshot or vps_get_backups, and it fails to mention the VPS context explicitly.

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 guidance is provided on when to use this tool or how it relates to alternatives such as vps_restore_snapshot. There are no exclusions, prerequisites, or alternative suggestions, leaving the agent without direction on tool selection.

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