restore_vm_snapshot

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

No behavioral traits disclosed beyond the bare action. This restore operation likely overwrites the VM, but description doesn't mention destructive nature, required permissions, or impact on current VM state. No annotations provided to compensate.

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?

Single sentence is very concise but lacks critical information. Not a model of efficiency; could include key details without much extra length.

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?

Given the restore operation's complexity and 5 parameters, the description is insufficient. No mention of return values (output schema exists but not referenced) or side effects.

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?

Zero parameter description: the input schema has 5 parameters but description adds no context on their meaning or usage. For example, 'restore_name' and 'snapshot_name' are not explained.

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?

Description clearly states the action: restore a VM from a VirtualMachineSnapshot. Verb 'restore' and resource 'VM from a VirtualMachineSnapshot' are specific and distinct from sibling tools like list_vm_snapshots or create_vm_snapshot.

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 on when to use this tool versus alternatives (e.g., create_vm_snapshot, list_vm_snapshots). No mention of prerequisites or when not to use it.

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