Veeam VBR v13 MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Start Instant Recovery' but doesn't explain what this entails—whether it's a temporary mount, requires specific permissions, has side effects, or involves rate limits. This leaves critical behavioral traits undocumented for a potentially complex 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, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it efficient and easy to parse, though it sacrifices detail for brevity.

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 implied by 'Instant Recovery' and the lack of annotations, output schema, and schema description coverage, the description is incomplete. It doesn't address what the tool returns, how it behaves, or what inputs are needed, making it inadequate for effective tool invocation in this context.

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 unspecified properties. The description adds no information about parameters, failing to compensate for the schema's lack of detail. This leaves the agent with no guidance on what data to provide for the recovery operation.

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 ('Microsoft Hyper-V VM'), which provides a basic understanding. However, it's vague about what 'Instant Recovery' entails and doesn't distinguish this tool from its siblings like 'InstantHvVMRecoveryMigrate' or 'InstantHvVMRecoveryUnmount', leaving ambiguity 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. The description lacks context about prerequisites, dependencies, or scenarios where this tool is appropriate compared to similar tools like 'EntireVmRestoreHv' or other recovery operations in the sibling list.

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