snap_delete

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

With no annotations, the description carries the burden of disclosing destructive behavior. It does say 'Delete' and 'Needs confirm=true,' which conveys that this is a destructive action requiring confirmation. However, it doesn't explicitly state irreversibility, that confirm=false means no deletion occurs, or the side effects mentioned in the allow_suspend parameter schema.

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 short sentences with no filler. It front-loads the core action ('Delete a snapshot') and immediately gives the critical invocation requirement ('Needs confirm=true'). Every part is useful.

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 rich input schema that documents every parameter, the description covers the essential purpose and the destructive confirmation gate. It doesn't mention return values or error behavior, but with no output schema and a clear destructive action, the missing pieces are minor and can be inferred from the schema.

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 100%, so the schema already documents all five parameters. The description adds emphasis on 'confirm=true' and 'optionally its children,' but these map directly onto existing schema parameters and don't provide substantial new semantic detail.

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 states a specific verb and resource: 'Delete a snapshot (and optionally its children).' It clearly distinguishes this from sibling tools like snap_take, snap_revert, and snap_list by naming the deletion action and the optional subtree scope.

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?

There is no guidance on when to use this tool versus alternatives such as snap_take or snap_revert. The mention of 'Needs confirm=true' is a prerequisite for invocation, not a usage rule that helps an agent choose between sibling snapshot tools.

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