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 mentions 'refresh their configuration,' implying a read/write operation that updates server states, but fails to disclose critical behaviors: whether this is disruptive (e.g., causes downtime), requires permissions, has side effects, or involves asynchronous processing. For a zero-parameter tool that likely triggers system-wide actions, this is a significant gap.

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 no wasted words. It front-loads the core action and purpose, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete for a tool that likely performs system-wide operations. It omits behavioral details (e.g., impact, async nature, permissions) and doesn't clarify the scope of 'configuration' refresh. For a zero-parameter tool with no structured safety hints, more context is needed to guide safe invocation.

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 zero parameters, and schema description coverage is 100% (empty schema). The description doesn't need to explain parameters, so it meets the baseline expectation. No additional parameter semantics are required or provided.

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 ('Rescan') and target ('all managed servers') with the specific purpose 'to refresh their configuration.' It distinguishes itself from sibling tools like 'RescanManagedServer' (singular) by specifying 'all' servers, though it doesn't explicitly compare to other rescan tools in the list.

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 'RescanManagedServer' (for individual servers) or 'RescanProtectionGroup'. It lacks context about prerequisites, timing, or consequences, leaving the agent with no usage criteria beyond the basic purpose.

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