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. It states 'add' implies a write operation, but lacks details on permissions required, whether the password is stored securely, if it overwrites existing passwords, or what the response looks like. This is a significant gap for a mutation tool with zero annotation coverage.

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 waste. It is appropriately sized and front-loaded, clearly stating the tool's 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 (mutation with nested object parameter), lack of annotations, 0% schema coverage, and no output schema, the description is inadequate. It should explain parameter details, behavioral traits, and usage context to be complete for this type of operation.

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 mentions no parameters. The input schema has one required parameter 'body' with an object type, but the description does not explain what properties 'body' should contain (e.g., password value, name, etc.). This fails to compensate for the low schema coverage.

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 'Add a new encryption password' clearly states the action (add) and resource (encryption password), distinguishing it from sibling tools like 'ChangeEncryptionPassword' or 'DeleteEncryptionPassword'. However, it lacks specificity about what an 'encryption password' is in this context (e.g., for backups, credentials, etc.), making it somewhat vague.

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 like 'ChangeEncryptionPassword' or 'DeleteEncryptionPassword', nor does it mention prerequisites (e.g., existing encryption setup) or constraints. Usage is implied only by the verb 'add', but explicit context is missing.

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