Restore snapshot

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

Annotations already indicate destructiveHint and readOnlyHint. The description adds critical behavioral details: irreversibility, data overwrite, possible service deploy, and key expiration. No contradictions.

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?

Six sentences, each adding valuable information. Could be slightly condensed, but effective. Front-loads purpose and key warnings. The API endpoint reference is useful but somewhat redundant.

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, so description should explain what the API returns (likely a success indication or restored snapshot). Missing return value information. InstanceId parameter context could be expanded for scaled services. Otherwise adequate.

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 67% (2 of 3 params described). The description adds meaningful context for snapshotKey (expiration and refresh), which is missing from schema. For diskId and instanceId, no additional details beyond schema. The added info compensates well.

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 tool's purpose: 'Restore snapshot. Restore a persistent disk to an available snapshot.' It specifies the resource (persistent disk) and action (restore), and mentions the API endpoint. No confusion with siblings as none perform restore.

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 provides key usage guidelines: it is irreversible, overwrites current disk data, may trigger a service deploy, and snapshot keys expire after 24 hours with instructions to refresh. It doesn't explicitly state when not to use, but the warnings serve as implicit guidance.

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