delete_snapshot_container

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

Since no annotations are provided, the description carries the full burden. It discloses the destructive nature and the confirm requirement, adding important behavioral context. However, it lacks details on irreversibility, permissions, or failure conditions.

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 brief sentences: the first states the action clearly, the second delivers the critical safety warning. There is no unnecessary wording.

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?

The tool is straightforward, but the description is minimal given the absence of annotations and low schema coverage. It provides the essentials for basic invocation but omits error scenarios, prerequisites, and consequence details.

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 0%. The description only adds meaning for the confirm parameter (must be true), while node, vmid, and snapname are left to their self-evident schema names without additional explanation.

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 uses the specific verb 'Delete' and clearly identifies the resource, 'an LXC container snapshot'. This distinguishes it from sibling tools like create_snapshot_container, rollback_snapshot_container, and list_snapshots_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 clearly implies usage for deleting a snapshot and states the required confirm=True for destructive operations. It does not explicitly mention alternatives or exclusion cases, which would be needed for a 5.

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