Veeam raw REST request (advanced)

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must fully disclose behavior. It mentions the read-only mode and cross-build compatibility, but does not disclose authentication needs, rate limits, or the potential for destructive operations (POST/PUT/DELETE/PATCH). The description adds some value but leaves gaps.

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 three sentences, each adding value: first defines purpose with examples, second gives usage instruction, third provides cross-build context and limitation. It is front-loaded and contains no filler.

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?

For a raw request tool with no output schema, the description should mention the return format (raw JSON response). It also lacks details on error handling or authentication. The sibling context is extensive, but the tool is an escape hatch for edge cases. Additional completeness would be beneficial.

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 coverage is 100%, so the schema describes all parameters. The description adds a path example ('/api/v1/failoverPlans') which is helpful but not essential. It does not significantly augment the schema definitions, so baseline 3 is appropriate.

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 it is an escape hatch for Veeam API endpoints not covered by dedicated tools, with specific examples like failover plans and SureBackup. It distinguishes itself from the extensive list of sibling tools that target specific operations.

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 explicitly says to use when no dedicated tool exists ('not covered by a dedicated tool'). It also mentions the read-only restriction ('only GET is permitted'). However, it does not explicitly list alternative dedicated tools to prefer, though this is implied by the sibling context.

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