delete_snapshot

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the destructive action (delete) and the confirmation requirement, but omits details about side effects, permissions, irreversibility, or what happens on failure. This leaves the agent underinformed for a deletion tool.

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 wasted words. The action is front-loaded, followed by immediate key requirements. Every sentence earns its place.

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 absence of annotations and the presence of an output schema (undescribed), the description lacks necessary context. It does not cover return values, error conditions, or the full behavioral implications of deletion. The agent would need additional knowledge to use this tool confidently.

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 has 0% description coverage, so the description's addition of the snapshot format (dataset@name) and confirmation requirement provides critical semantic information beyond the schema's type definitions. For 2 parameters, this adds significant value.

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 it deletes a snapshot, distinguishing it from sibling tools like create_snapshot, rollback_snapshot, and list_snapshots. The verb 'Delete' and resource 'snapshot' are specific and unambiguous.

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 explicitly requires confirm=True and specifies the snapshot format (dataset@name). While it lacks explicit exclusions or when-not-to-use guidance, the requirement is strong enough to guide proper usage. It implies the tool is for direct deletion only, not for other snapshot operations.

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