rollback_container_snapshot

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

Annotations already indicate destructiveHint=true and idempotentHint=false. The description adds that it 'Discards changes since then,' which elaborates on the destructive nature, but does not provide additional behavioral details such as whether the snapshot itself is deleted or how state is restored. No contradiction with annotations.

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 two sentences plus a requirement line, all concise and front-loaded. No redundant information; every sentence adds value.

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 straightforward rollback operation, the description is reasonably complete: it specifies the action, resource, effect, and a critical prerequisite. The presence of an output schema (not shown) may cover return values. Minor missing context: no mention of what happens to the snapshot after rollback, but not critical.

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?

Input schema has 100% description coverage for all three parameters. The description adds little beyond the schema; the snapname description repeats the discard concept from the main description. Parameter semantics are adequately handled by 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 clearly states the action ('Roll back an LXC container to a snapshot') and the resource (LXC container snapshot), and the phrase 'Discards changes since then' reinforces the purpose. It distinguishes from sibling tool 'rollback_vm_snapshot' by specifying LXC container.

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 mentions 'Requires PROXMOX_RISK_LEVEL=all' as a prerequisite, but does not provide explicit guidance on when to use this tool versus alternatives like creating or deleting snapshots. There is no when-not-to-use or mention of other context-specific conditions.

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