delete_container_snapshot

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

No annotations provided, so the description must disclose behavioral traits. It only states the action and lists parameters, omitting details like effects of 'force', error conditions, or return value. This is insufficient for a mutating operation.

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 short with a clear purpose sentence followed by a list of args. While concise, it could be better structured with front-loaded key details.

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 tool's complexity (4 params, none described in schema) and lack of annotations, the description is incomplete. It doesn't address prerequisites, side effects, or output schema (which exists but is not mentioned).

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 coverage is 0% (no parameter descriptions), so the description's explanations ('node: The node name', 'force: Force delete') add some meaning beyond type/name. However, explanations are minimal and vague, especially for 'force'.

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 a container snapshot,' which specifies the verb and resource. It distinguishes from sibling tools like 'delete_vm_snapshot' (VM snapshots) and 'delete_container' (entire containers).

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 is given on when to use this tool, such as prerequisites (snapshot existence) or when to use 'force' vs not. Among siblings like 'rollback_container_snapshot', there is no differentiation.

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