lattice_delete_database_instance

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

With no annotations, the description carries the full burden. It clearly states the destructive nature ('data is lost unless a snapshot exists'), which is the key behavioral trait. However, it does not disclose other aspects like permission requirements or irreversibility, which would be needed for a 5.

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 extremely concise with three short sentences: purpose, consequence, and recommendation. Every sentence serves a distinct purpose (action, warning, prerequisite), and the most critical information is front-loaded.

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 simplicity of the tool (one parameter, no output schema, no annotations), the description covers the core needs: purpose, destructive impact, and a safety net. It lacks details on return values or error scenarios, but those are not critical for this single-action tool.

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 description adds no extra meaning beyond what the schema provides. The schema already describes 'id' as 'Database instance ID'—the description does not elaborate on format, constraints, or usage tips, meeting the baseline but not exceeding it.

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 verb 'Delete' and the resource 'database instance record', making the purpose unambiguous. It distinguishes itself by warning about data loss and recommending a prerequisite check, which helps differentiate from related tools like lattice_delete_database_snapshot.

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 provides explicit guidance on when to use this tool: after checking snapshots via lattice_list_database_snapshots. It does not list alternatives but the context is sufficient for safe usage. A slightly higher score would require explicit exclusions or comparison with sibling tools.

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