Delete Backup

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

The annotations already indicate destructiveHint=true and openWorldHint=true. The description adds a meaningful behavioral detail by stating 'This action cannot be undone,' which clarifies the permanence beyond the generic destructive annotation. This is useful context for an agent deciding whether to proceed.

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 very brief: two short sentences. The first sentence restates the title, but the second sentence carries important irreversibility information. There is no wasted content, though the redundancy with the title prevents a 5.

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 single-parameter delete operation, the description covers the key behavioral fact (irreversibility) and the schema covers the parameter. No output schema exists, so return values are not a gap. It could be improved by referencing how to obtain a backup_id, but the overall context is adequate.

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%, with backup_id described as 'The backup ID to delete.' The description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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 states a specific verb and resource: 'Delete a backup.' It clearly identifies the action and is distinct among backup siblings such as kinsta_backups_list, kinsta_backups_create, and kinsta_backups_restore. However, it does not explicitly differentiate itself from other delete tools or mention scope, so it stops short of a 5.

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 no guidance on when to use this tool versus alternatives. It does not mention that it should be used only when a backup should be permanently removed, nor does it reference related operations like restore or list. The use case is implied by the name but not explicitly stated.

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