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 of behavioral disclosure. It states the tool starts a recovery process but fails to describe what this entails—such as whether it mounts a VM, requires specific permissions, has side effects, or involves time-sensitive operations. For a tool with 'Recovery' in its name and no annotations, this lack of detail is inadequate.

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. It is front-loaded with the core action and resource, making it efficient to parse. However, this conciseness comes at the cost of completeness, as it lacks necessary details.

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 VM recovery), lack of annotations, 0% schema coverage, no output schema, and presence of sibling tools, the description is incomplete. It omits critical context such as parameter meanings, behavioral traits, and usage distinctions, making it insufficient for an agent to use the tool effectively.

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 on its structure. The description provides no information about parameters, not even hinting at what 'body' should contain (e.g., VM identifiers, recovery options). With low schema coverage, the description fails to compensate, leaving parameters entirely undocumented.

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 resource ('VMware vSphere VM'), which provides a basic understanding of purpose. However, it lacks specificity about what 'Instant Recovery' entails operationally and doesn't differentiate from sibling tools like 'InstantViVMRecoveryMigrate' or 'InstantViVMRecoveryUnmount', leaving ambiguity about when to use this specific tool versus alternatives.

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 does not mention prerequisites, conditions for use, or exclusions. Given sibling tools like 'InstantViVMRecoveryMigrate' and 'InstantViVMRecoveryUnmount', the lack of differentiation is a significant gap, leaving the agent without context for tool selection.

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