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. The description only states what the tool does at a high level ('Get all task sessions') but fails to disclose critical behavioral traits such as whether this is a read-only operation, if it requires specific permissions, how it handles large datasets (e.g., pagination via skip/limit parameters), or what the output format looks like. This leaves significant gaps for a tool with four parameters.

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—a single sentence with no wasted words. It is front-loaded with the core action ('Get all task sessions'), though this conciseness comes at the cost of completeness. Every word earns its place, but the description is under-specified rather than efficiently informative.

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 complexity (a retrieval tool with four parameters), lack of annotations, 0% schema description coverage, and no output schema, the description is completely inadequate. It doesn't explain what 'task sessions' are, how to use the parameters, what the tool returns, or any behavioral context, making it insufficient 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 four parameters (skip, limit, stateFilter, resultFilter) with 0% schema description coverage, meaning none have descriptions in the schema. The tool description provides no information about any parameters, their purposes, valid values (e.g., what stateFilter or resultFilter accept), or how they affect the retrieval. This fails to compensate for the lack of schema documentation.

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 'Get all task sessions across all sessions' is a tautology that essentially restates the tool name 'GetAllTaskSessions' with minor elaboration. It doesn't specify what a 'task session' is or what resource it operates on, nor does it distinguish this tool from sibling tools like 'GetAllSessions' or 'GetSessionTaskSessionsWithFiltering' that appear related. The purpose remains vague beyond the literal name.

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?

There is no guidance on when to use this tool versus alternatives. The description doesn't mention any prerequisites, context for usage, or comparisons to sibling tools like 'GetAllSessions' or 'GetSessionTaskSessionsWithFiltering', leaving the agent with no information to make an informed choice among potentially overlapping retrieval tools.

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