delete_container_snapshot

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

The description adds the explicit warning 'Irreversible', which goes beyond the annotations (destructiveHint=true). It also mentions the risk level requirement. However, it does not describe other behavioral aspects like error conditions or side effects.

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 long, each providing essential information without any fluff. It is front-loaded with the primary action and immediately followed by critical caveats.

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 simple delete operation, the description covers the core purpose, irreversibility, and a prerequisite (risk level). The output schema likely handles return values. It lacks details on error states or dependencies, but this is acceptable for the tool's simplicity.

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?

The input schema already provides clear descriptions for all 3 parameters (100% coverage). The description does not add any new semantic information beyond what the schema provides, so it meets the baseline.

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 'Delete' and the resource 'LXC container snapshot', distinguishing it from sibling tools like create_container_snapshot and rollback_container_snapshot. The added caveats 'Irreversible' and risk level requirement further clarify the purpose.

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 the risk level requirement, which is a precondition, but does not explicitly state when to use this tool versus alternatives or when not to use it. Usage is implied by the tool name and action.

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