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 full burden for behavioral disclosure but offers minimal information. It states this is a read operation ('Get'), implying it's non-destructive, but doesn't describe what 'mount sessions' entail, potential side effects, authentication needs, rate limits, or return format. For a tool with zero annotation coverage, this 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, focused sentence with no wasted words. It's front-loaded with the core purpose ('Get all mount sessions'), 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 (Azure instant recovery context), lack of annotations, no output schema, and a parameter with 0% schema coverage, the description is insufficient. It doesn't compensate for missing structured data, leaving the agent without needed context on behavior, parameters, or results.

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 description mentions no parameters, while the schema has one required parameter (mountId) with 0% description coverage. The description fails to explain what 'mountId' represents, its format, or how it relates to retrieving 'all mount sessions', leaving the parameter's purpose and usage 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 ('Get all') and resource ('mount sessions for Azure instant recovery'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'GetAllAzureInstantVMRecoveryMounts' or 'GetAzureInstantVMRecoveryMount', but the specificity of 'mount sessions' provides some distinction from general mount operations.

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. It doesn't mention prerequisites, context for usage, or compare it to related sibling tools like 'GetAllAzureInstantVMRecoveryMounts' or 'GetAzureInstantVMRecoveryMount', leaving the agent without usage direction.

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