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 'Create' which implies a write operation, but doesn't clarify permissions needed, whether the token is reusable, expiration details, or what happens on failure. For a mutation tool with zero annotation coverage, this is insufficient.

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 with zero wasted words. It's appropriately sized for a simple tool and front-loads the core purpose without unnecessary elaboration.

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 (a mutation with a nested object parameter), lack of annotations, 0% schema coverage, and no output schema, the description is inadequate. It doesn't compensate for missing structured data, leaving key aspects like parameter details, behavioral traits, and output undefined.

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%, and the description provides no information about the single parameter 'body' (a nested object). The description doesn't explain what properties 'body' should contain (e.g., computer identifier, token settings) or their semantics, leaving parameters completely 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 clearly states the action ('Create') and target resource ('recovery token for a protected computer'), providing a specific verb+resource combination. It doesn't explicitly differentiate from sibling tools like 'DeleteComputerRecoveryToken' or 'UpdateComputerRecoveryToken', but the action is distinct enough to imply its purpose.

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 doesn't mention prerequisites (e.g., needing a protected computer), exclusions, or refer to sibling tools like 'DeleteComputerRecoveryToken' or 'GetComputerRecoveryToken' for context.

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