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 the full burden of behavioral disclosure but offers minimal insight. It doesn't indicate if this is a read-only or destructive operation, what permissions are required, whether it's asynchronous, or what side effects occur (e.g., mounting a disk). The term 'Start' implies an initiation but lacks details on execution flow or outcomes.

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 extremely concise with a single sentence, 'Start instant FCD recovery.', which is front-loaded and wastes no words. However, this brevity comes at the cost of clarity and completeness, but it meets the criteria for conciseness by being minimal and direct.

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 (inferred from the name involving VMware FCD and sessions), lack of annotations, 0% schema coverage, no output schema, and a vague description, the description is highly incomplete. It doesn't explain what the tool does in detail, how to use it, what parameters are needed, or what to expect, making it inadequate for effective agent 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 input schema has 0% description coverage with one parameter ('body') as a nested object with unspecified properties. The description provides no information about what 'body' should contain (e.g., recovery target, session details, or configuration), failing to compensate for the schema's lack of documentation and leaving parameters entirely 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 'Start instant FCD recovery' states a general action but lacks specificity about what 'FCD' refers to (likely VMware First Class Disks) and what 'recovery' entails. It doesn't distinguish this tool from sibling tools like 'InstantRecoveryVmwareFcdDismountWithSession' or 'InstantRecoveryVmwareFcdMigrateWithSession', making it a vague purpose statement rather than a clear 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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context (e.g., after a failure), or exclusions, and it fails to reference sibling tools like 'InstantRecoveryVmwareFcdDismountWithSession' for dismounting, leaving the agent with no usage direction.

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