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. It states this is a 'Get' operation but doesn't disclose behavioral traits like whether it's read-only, pagination behavior (implied by skip/limit parameters but not explained), authentication requirements, rate limits, or what happens with large result sets. For a list operation with parameters, this is inadequate.

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 states the core purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information, making it highly concise.

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 2 parameters with 0% schema coverage, no annotations, no output schema, and a list operation that likely returns structured data, the description is incomplete. It doesn't address parameter usage, return format, pagination, or behavioral constraints, leaving significant gaps for the agent.

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%, so parameters 'skip' and 'limit' are undocumented in the schema. The description doesn't mention these parameters at all, failing to compensate for the schema gap. It doesn't explain what 'skip' and 'limit' mean in context of getting data sources, leaving their semantics unclear.

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 unstructured data sources (file servers, NAS)', making the purpose unambiguous. It doesn't explicitly differentiate from sibling tools like 'GetUnstructuredDataServer' (singular) or 'CreateUnstructuredDataServer', but the 'all' scope 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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context for usage, or compare it to sibling tools like 'GetUnstructuredDataServer' (singular) or 'BrowseCloudEntity'. This leaves the agent without usage context.

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