lattice_delete_backup_destination

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

With no annotations, the description carries full burden. It discloses that instances pointing to the backup destination lose their target and labels the action as 'Destructive'. This provides essential behavioral context but lacks details on irreversibility, permission requirements, or potential cascading effects beyond instances.

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?

Two sentences with no wasted words. First sentence states the core action, second adds a critical side effect. Front-loaded and efficient.

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 tool with one parameter and no output schema, the description covers the essential points: what is deleted, its destructive nature, and the consequence for associated instances. Could be slightly improved by explicitly stating that deletion is irreversible, but 'destructive' implies that.

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 100% for the single parameter 'id' (Backup destination ID). The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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?

Description clearly states the action 'Delete a backup destination', which is a specific verb+resource. It distinguishes from sibling delete tools (e.g., delete_stack, delete_api_token) by naming the resource type. However, it could be more precise by specifying that deletion is by ID.

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 guidance on when to use this tool versus alternatives like lattice_update_backup_destination or lattice_list_backup_destinations. Does not mention prerequisites (e.g., need to reassign instances before deletion) or situations where it should not be used.

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