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

Annotations already declare this as a safe read-only, idempotent operation. The description adds substantial value beyond that by documenting return ordering, returned fields, the reason and exportState enumerations, and the user-facing convention to identify backups by time and reason rather than backupId.

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?

Two dense sentences, front-loaded with the primary behavior and returned data, followed by concrete next-tool routing and a naming rule. No sentence is wasted.

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?

No output schema exists, so the description supplies the essential return fields, ordering, and enum states. Together with the schema-provided serverId description, an agent has enough information to list and interpret backups correctly.

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 only required parameter is serverId inside a path object, and the schema already describes it as the id from listServers. The description does not mention the parameter at all, so it adds no semantic guidance, though the parameter is simple enough that this is a minor gap.

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?

States a specific verb and resource ("Lists backups"), adds ordering ("newest first"), and names the returned fields, which clearly distinguishes it from sibling mutation and restore tools.

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?

Explicitly routes the agent: pass backupId to restoreBackup, cancelBackupRestore, startBackupExport, getBackupDownloadUrl, or deleteBackup, and calls out that getBackupDownloadUrl requires exportState ready.

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