Get VPS Backups

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

With no annotations provided, the description should disclose behavioral traits such as read-only nature, permissions, or pagination. It only says 'List backups,' which hints at read-only but omits any safety or side-effect details. The lack of explicit non-destructive labeling or additional behavioral context lowers the score.

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 concise sentence that conveys the core action with no extraneous words. It is perfectly sized for a simple list operation.

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 one-parameter list tool with no output schema, the description is adequate but minimal. It doesn't specify the return format, pagination, or any constraints, though the simplicity of the operation makes this gap less critical. A slightly richer description would improve completeness.

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% and the vm_id parameter is described as 'Virtual machine ID' in the schema. The description does not add any extra meaning to the parameter, but the baseline of 3 applies because the schema already fully documents it.

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 states a specific verb ('List') and resource ('backups for a virtual machine'), clearly distinguishing it from sibling tools like vps_restore_backup or vps_create_snapshot. The purpose is immediately unambiguous.

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 implies use when backups need to be listed, but it does not explicitly contrast with related tools such as vps_get_snapshot or vps_restore_backup. No when-not-to-use guidance or alternative tool mentions are provided.

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