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 must fully disclose behavioral traits. It only states the action without details on permissions required, whether it's destructive, rate limits, or what the operation entails (e.g., if it mounts a VM temporarily). This leaves critical behavioral aspects undocumented.

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, clear sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core action without unnecessary elaboration.

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 (involving Azure VM recovery), no annotations, a schema with 0% coverage, no output schema, and a vague description, it is severely incomplete. The agent lacks essential details on behavior, parameters, and expected outcomes, making it inadequate for safe and effective 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?

The input schema has 0% description coverage with one parameter ('body') as a nested object with no defined properties. The description adds no information about what 'body' should contain, such as VM identifiers, recovery settings, or Azure configuration, failing to compensate for the schema's lack of detail.

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 states the action ('Start Instant Recovery') and target ('to Microsoft Azure'), providing a basic purpose. However, it's vague about what 'Instant Recovery' entails compared to sibling tools like 'AzureInstantVMRecoveryMigrate' or 'AzureInstantVMRecoveryUnmount', lacking specificity on the exact operation (e.g., mounting a VM for recovery vs. migrating it).

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 such as 'AzureInstantVMRecoveryMigrate' or 'AzureInstantVMRecoveryUnmount'. The description does not mention prerequisites, context, or exclusions, leaving the agent without usage direction.

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