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 states the tool stops publishing/unmounts a VM, implying a destructive operation that likely changes system state, but doesn't specify effects like whether data is preserved, permissions required, or error conditions. This leaves significant gaps for safe agent invocation.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 (destructive operation, 2 parameters with 0% schema coverage, no output schema, and no annotations), the description is inadequate. It lacks details on parameters, behavioral outcomes, error handling, and relationships with sibling tools, making it incomplete for reliable agent 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%, so the description must compensate for undocumented parameters. It provides no information about the 'mountId' (required) or 'body' (optional object) parameters, their formats, or purposes. This fails to add meaning beyond the bare schema, leaving parameters semantically unclear.

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 clearly states the action ('Stop publishing') and resource ('a Hyper-V VM') with the specific operation 'unmount' in parentheses. It distinguishes from sibling tools like 'InstantHvVMRecoveryMount' by indicating an opposite operation, though it doesn't explicitly compare to all alternatives like 'InstantHvVMRecoveryMigrate'.

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 'InstantHvVMRecoveryMigrate' or other unmount tools for different platforms (e.g., 'AzureInstantVMRecoveryUnmount'). The description implies usage for stopping VM publishing but lacks context on prerequisites, dependencies, or exclusions.

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