Создание бэкапа диска

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

Discloses asynchronous behavior and the status lifecycle (create → done) that is not present in annotations. This is valuable beyond what annotations offer, helping the agent understand immediate return and delayed completion.

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 concise sentences: first states the purpose, second adds behavioral and usage guidance. No wasted words, each sentence earns its place.

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 create tool, it covers purpose, async behavior, and usage context. It does not describe the return value, but given no output schema and clear status flow, it is sufficiently complete for agent decision-making.

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 covers all parameters with descriptions (100% coverage), so the description adds no additional parameter semantics. It correctly relies on the schema for parameter details.

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 ('Создаёт'), the object ('ручной бэкап диска VPS'), and includes the async status transition, making it specific and distinct from sibling backup tools like delete_server_disk_backup.

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?

Explicitly states when to use: 'Используй перед рискованными операциями (миграция, обновление ОС)'. It provides clear context, though it doesn't mention when-not or alternatives, which are less relevant given no competing create backup tool exists.

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