delete_snapshot

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

With no annotations, the description carries the full burden of behavioral disclosure for a destructive operation, and it says nothing about irreversibility, required permissions, batch behavior of the ids array, or interaction with the recycle bin. It only implies mutation via the verb 'Delete'.

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 single phrase is front-loaded and waste-free, but its brevity stems from under-specification rather than disciplined editing. It is appropriately sized only in the sense that there is almost nothing to say.

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 tool with no annotations, no output schema, and one undocumented required parameter, the description is far too thin. An agent gets no confirmation of what happens after deletion or how to obtain valid snapshot IDs.

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%, so the schema documents only types; the description adds nothing about the required 'ids' array (format, whether multiple snapshots can be deleted at once, or ID source). It also describes a singular 'snapshot' while the parameter is a plural array, adding ambiguity.

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?

States a specific verb and resource ('Delete ... snapshot'), so the agent knows the operation is a removal of snapshots. It does not, however, distinguish this from adjacent siblings such as recover_snapshot, recreate_snapshot, or load_snapshot, nor does it clarify the 'system snapshot' concept.

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 when-to-use guidance, no warning about when deletion is inappropriate, and no pointer to alternatives like recover_snapshot or the recycle bin. The agent must infer usage entirely from the name.

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