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 full burden. It fails to disclose critical behavioral traits: whether this is a read-only or destructive operation, what permissions are needed, if it's asynchronous, rate limits, or what happens during migration. 'Start' implies an initiation but gives no details on execution or outcomes.

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 extremely concise with a single sentence 'Start FCD disk migration.' It's front-loaded and wastes no words, though this brevity contributes to under-specification rather than clarity.

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 tool's complexity (migration operation with nested parameters), lack of annotations, 0% schema coverage, and no output schema, the description is completely inadequate. It doesn't cover behavior, parameters, or expected results, failing to provide necessary context for safe and correct use.

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 0%, with 2 parameters (mountId and body) undocumented in both schema and description. The description adds no meaning beyond the schema—it doesn't explain what mountId refers to or what the body object should contain, leaving parameters semantically opaque.

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 'Start FCD disk migration' states a verb ('Start') and resource ('FCD disk migration'), but it's vague about what 'FCD' means (likely VMware First Class Disks) and lacks specificity on the migration context. It doesn't distinguish from siblings like 'InstantRecoveryVmwareFcdMountWithSession' or 'InstantRecoveryVmwareFcdDismountWithSession', leaving the exact purpose unclear.

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. The description doesn't mention prerequisites, context (e.g., after mounting), or exclusions, making it hard for an agent to decide when to invoke it among related recovery tools.

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