Get backups

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the context that this is for viewing backup points for VPS data recovery, but it does not disclose additional behavioral details like pagination behavior, response structure, or backup ordering. No contradiction with annotations.

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 only two sentences long, front-loads the core operation in the first sentence, and the second sentence adds useful use-case context without redundancy or fluff. Every line earns its place.

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 simple, read-only, list-style endpoint with complete parameter descriptions and safe annotations, the description is largely sufficient. It clearly conveys the resource and purpose. However, with no output schema, a bit more detail about the response shape or pagination behavior could improve completeness, though it is not critically missing.

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 100%: both virtualMachineId and page have descriptions. The description only adds the phrase 'for a specified virtual machine,' which slightly reinforces the virtualMachineId parameter but adds no meaning beyond the schema. 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 the operation: 'Retrieve backups for a specified virtual machine.' It also adds 'view available backup points for VPS data recovery,' which reinforces that this is a read-only inspection tool rather than a restore action, distinguishing it from the sibling VPS_restoreBackupV1.

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 gives clear usage context: use this endpoint to view available backup points. However, it does not explicitly mention alternatives or state when not to use it, such as directing restore operations to VPS_restoreBackupV1. This is clear context without explicit exclusions.

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