lattice_delete_database_snapshot

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

The description conveys the key behavioral trait (irreversible deletion) with the note 'Destructive — that restore point is gone.' However, with no annotations, it lacks details on permissions, side effects, or async behavior.

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?

Extremely concise with two short sentences. No filler or redundant information.

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 simple delete operation, the description covers the essential purpose and consequence. Missing context includes how to retrieve the snapshot ID, synchronous vs async execution, and return value.

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 100%, so the parameter 'snapshot_id' is documented. The description adds no extra meaning about how to obtain or validate the snapshot ID.

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 database snapshot') and highlights the destructive nature, distinguishing it from related tools like create or restore.

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 explicit guidance on when to use this tool versus alternatives, such as restoring instead of deleting. Only a warning about destructiveness, but no prerequisites or context.

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