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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is known without the description. The description adds nothing beyond repeating the destructive nature — no statement about irreversibility, whether dependent machines are affected, or what happens if the id does not exist.

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?

Three words contain no filler, but the size is driven by under-specification rather than efficiency. There is no structure or front-loaded context beyond the bare verb-object phrase.

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 destructive, irreversible operation with an undocumented identifier parameter and no output schema, the definition is far too thin. The annotations cover the safety profile, but the description should at least identify what the id names and what state remains after deletion.

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 single required parameter 'id' has 0% schema description coverage, and the description never mentions it. It is left ambiguous whether the id refers to a snapshot, a machine, or a template, which is the one piece of meaning this short description needed to supply.

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 gives a specific verb (Erase) and resource (snapshot), so an agent knows exactly what object it acts on. It does not distinguish this from sibling deletion tools such as machine_delete or template_delete, which keeps it out of the top band.

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 about when to use this versus listing snapshots first, creating a backup, or using other delete tools. No prerequisites or exclusions are stated, leaving the agent to infer selection entirely from context.

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