list_backups

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

The description implies a read-only operation by using 'list', but with no annotations provided, it does not explicitly state the lack of side effects, authentication requirements, or other behavioral traits. The mention of 'legacy VPS server' adds some context, but more disclosure would be beneficial.

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 sentence that effectively states the main purpose and use cases. No redundant information; every part serves a purpose. Front-loaded with the primary action and resource.

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 list tool with one parameter and no output schema, the description adequately covers the tool's purpose and usage. However, it does not describe the structure of the returned backup list (e.g., fields like backup ID, date) or mention pagination. Slightly incomplete given the absence of an output schema.

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% with a clear description for service_id. The tool description adds minimal extra context by referring to 'legacy VPS server', but the baseline is met. No additional parameter explanation needed beyond the schema.

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?

Clearly states the tool lists existing backups for a single legacy VPS server. The description distinguishes it from sibling tools by specifying the resource type and action, and there are no other list_backups tools in the sibling list.

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?

Provides explicit use cases: checking for a recent backup before risky changes or finding a backup ID for restore. However, it does not mention when not to use this tool or suggest alternative tools for related tasks (e.g., creating backups).

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