Veeam VBR v13 MCP Server

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is destructive (e.g., commits migration), requires specific permissions, has side effects, or involves rate limits. The term 'Start migrating' implies an ongoing process but lacks clarity on completion 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 a single, direct sentence with no wasted words. It's front-loaded with the core action and resource, making it efficient and easy to parse, though this brevity contributes to gaps in other dimensions.

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 2 parameters, nested objects, no output schema, and no annotations), the description is inadequate. It lacks details on behavior, parameters, output, and integration with sibling tools, making it insufficient for safe and effective use by an 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?

Schema description coverage is 0%, so the description must compensate but provides no parameter information. It doesn't explain what 'mountId' or 'body' represent, their formats, or required content (e.g., migration target settings). This leaves both parameters entirely undocumented, failing to add any semantic value.

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 migrating') and target resource ('Hyper-V instant recovery VM'), which provides a basic purpose. However, it doesn't specify what migration entails (e.g., to production, to another host) or differentiate from sibling tools like 'InstantHvVMRecoveryMount' or 'InstantHvVMRecoveryUnmount', making it vague about the specific operation.

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. It doesn't mention prerequisites (e.g., requiring a mount first), exclusions, or related tools like 'InstantHvVMRecoveryMount' for setup, leaving the agent with no context for appropriate usage.

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