Удаление бэкапа диска

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

The description explicitly states 'Действие необратимо' (the action is irreversible), which is important behavioral context. However, the annotation `destructiveHint: false` contradicts this claim, as deleting a backup is inherently destructive. This is a direct contradiction, so the score is 1.

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 concise, consisting of two sentences that front-load the main purpose and then add a crucial warning. Every word earns its place with no redundancy.

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 with no output schema, the description covers the action, irreversibility, and a safeguard to verify before deletion. It lacks mention of permissions or response format, but that is not critical for this 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 description coverage is 100%, meaning the schema fully documents the required parameters (server_id, disk_id, backup_id). The description adds no additional parameter-specific meaning, so the baseline score 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 clearly states the action: 'Удаляет бэкап диска сервера' (deletes a server disk backup). It uses a specific verb and resource, distinguishing it from siblings like create_server_disk_backup or list_server_disk_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 description advises checking via list_server_disk_backups before deleting to ensure it is not the last actual backup, providing practical usage context. However, it does not explicitly exclude when to use this tool or mention alternatives.

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