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 retrieves 'active' mount points, implying a read-only operation, but does not clarify if it requires specific permissions, how it handles pagination (given 'skip' and 'limit' parameters), or what the output format is. This leaves significant gaps for a tool with parameters and no output schema.

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. Every part of the sentence contributes directly to stating the tool's purpose, earning its place effectively.

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 has parameters with no schema descriptions, no annotations, and no output schema, the description is incomplete. It does not explain the parameters, behavioral details like pagination or permissions, or what is returned, making it inadequate for a tool with this complexity and lack of structured support.

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 two parameters ('skip' and 'limit') with 0% description coverage, meaning their purposes are undocumented in the schema. The description does not mention these parameters at all, failing to compensate for the low coverage. It adds no semantic information beyond what the schema provides, leaving parameters ambiguous.

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 verb ('Get') and resource ('all active instant recovery mount points for Azure VMs'), making the purpose specific and understandable. However, it does not explicitly distinguish this tool from its sibling 'GetAllAzureInstantVMRecoveryMountSessions', which appears to be a related but distinct operation, so it misses full sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives, such as the sibling 'GetAllAzureInstantVMRecoveryMountSessions' or other instant recovery mount tools for different platforms (e.g., 'GetAllInstantHvVMRecoveryMounts'). There is no mention of prerequisites, context, or exclusions, leaving usage unclear.

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