delete_vps_backup

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

Adds behavioral context beyond the destructiveHint=true annotation by disclosing that the delete is permanent/irreversible and guarded by confirm=true. No contradiction with annotations.

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?

One sentence with zero filler. The action and consequence are front-loaded, and the confirm requirement is stated compactly.

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 annotations, the description covers the action, permanence, and confirmation guard. It omits response or error details, but no output schema exists and the operation is straightforward.

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?

With 0% schema description coverage, the description partially compensates by explaining that confirm must be true to execute the deletion. vps_id and backup_id are only implied via 'this VPS' and 'one backup', and their names already carry most of the meaning.

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?

States a specific verb ('Permanently delete') and resource ('one backup of this VPS'), making the action unambiguous. It clearly distinguishes from sibling tools like create_vps_backup, restore_vps_backup, and list_vps_backups.

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 usage context is implied: use this to delete a single backup. It provides one clear condition, 'requires confirm=true', but does not explicitly name alternatives or state when to prefer list_vps_backups or restore_vps_backup.

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