Veeam VBR v13 MCP Server

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

No annotations are provided, so the description carries the full burden. It states 'Restore' which implies a write/mutation operation, but doesn't disclose critical behavioral traits such as required permissions, whether it overwrites existing VMs, rate limits, or what the restore process entails (e.g., from backup, point-in-time). This leaves significant gaps for a destructive operation.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized for its content, earning its place with zero waste.

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?

Given the complexity of a VM restore operation, no annotations, no output schema, and 0% schema coverage with 1 undocumented parameter, the description is incomplete. It lacks details on behavior, parameters, and expected outcomes, making it insufficient for safe and effective use by an AI agent.

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?

The input schema has 1 parameter ('body') with 0% description coverage and no details in the schema. The description adds no information about parameters, such as what 'body' should contain (e.g., VM ID, restore point, target location). With low schema coverage and no compensation in the description, this is inadequate.

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 'Restore an entire VMware vSphere VM' clearly states the action (restore) and target (VMware vSphere VM), which is better than a tautology. However, it lacks specificity about what 'entire' entails (e.g., full VM vs. files) and doesn't distinguish from sibling tools like 'EntireVmRestoreCloudDirector' or 'EntireVmRestoreHv', making it vague in context.

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?

No guidance is provided on when to use this tool versus alternatives like 'EntireVmRestoreCloudDirector' or 'EntireVmRestoreHv', nor does it mention prerequisites or context for restoration. The description implies usage for VMware vSphere VMs but offers no explicit when/when-not instructions or named alternatives.

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