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 full burden. 'Start an immediate configuration backup' implies a write/mutation operation, but it doesn't disclose whether this requires admin permissions, if it's asynchronous, what happens if a backup is already running, or if it impacts system performance. For a tool with zero annotation coverage, this leaves critical behavioral gaps.

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 action. It's front-loaded with the core purpose and contains no redundant or unnecessary information, making it optimally concise for a zero-parameter tool.

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 'configuration backup' in a system with many sibling tools, the description is insufficient. It lacks output details (no schema provided), doesn't explain what 'configuration' includes, and offers no context on prerequisites, side effects, or success criteria. For a mutation tool with no annotations or output schema, this leaves the agent under-informed.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the input requirements. The description doesn't need to add parameter details, but it appropriately doesn't mention any parameters either. A baseline of 4 is given since no parameters exist to document.

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 ('Start') and the target ('configuration backup'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential siblings like 'GetConfigBackupOptions' or 'UpdateConfigBackupOptions', which would require more specific context about what makes this backup 'immediate' versus scheduled alternatives.

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. With siblings like 'StartJob', 'StartHealthCheckBackup', and 'StartMalwareBackupScan', there's no indication of whether this is for ad-hoc backups, emergency scenarios, or routine maintenance. The agent must infer usage from the name alone.

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