start_vm_restore

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

With no annotations, the description fully discloses that the operation is a write, irreversible, runs as an async session, and may refuse to overwrite the VBR host. Also explains the dry_run preview behavior.

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?

Long but well-structured with a clear opening warning, logical flow, and minimal redundancy. Could be slightly tighter but every sentence adds value.

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?

Covers the operation well: mentions async polling, irreversibility, and parameter semantics. No output schema, but the description indicates how to check results via session tools, which is sufficient.

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 has 0% description coverage, but the description explains all three parameters: restore_point_id (referenced to restore_list_points), dry_run (detailed preview behavior), and target (Veeam target name).

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?

Specifically states 'start a VM restore from a restore point', uses a clear verb-resource pair, and distinguishes from sibling tools by focusing on restore operations and async sessions.

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 directs to confirm with user due to irreversibility, explains use of dry_run for preview, and provides a safety warning about the VBR host overwrite check. No when-not-to-use stated, but the guidance is comprehensive.

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