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 data ('Get'), implying a read-only operation, but does not specify whether it requires authentication, has rate limits, returns paginated results, or details the output format. For a tool with three parameters and no annotations, this is a significant gap in transparency.

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 front-loaded with the core action and resource, making it easy to parse quickly. There is no wasted verbiage or redundant information.

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 three parameters with 0% schema coverage, no annotations, and no output schema, the description is insufficient. It does not explain parameter usage, behavioral traits like pagination or filtering, or the return format. For a retrieval tool with filtering capabilities, more context is needed to guide effective 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?

The schema description coverage is 0%, meaning none of the three parameters (skip, limit, nameFilter) are documented in the schema. The description does not mention any parameters, failing to compensate for this gap. It provides no information on what these parameters do, their expected values, or how they affect the retrieval of encryption passwords.

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 encryption passwords configured on the Veeam Backup server'), making the purpose specific and understandable. It does not explicitly differentiate from sibling tools like 'GetEncryptionPassword' (singular) or 'ExportEncryptionPasswords', but the scope ('all') is implied. This is clear but lacks explicit 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. It does not mention prerequisites, context for usage, or compare it to sibling tools like 'GetEncryptionPassword' (for a single password) or 'ExportEncryptionPasswords' (for export functionality). Without such guidance, the agent must infer usage from the name and description alone.

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