Restore Backup

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

With no annotations, the description carries the burden. It reveals two modes and parameter requirements but does not disclose potential destructive effects of restore or what planning returns. More detail on behavior is needed.

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 extremely concise (two short sentences), front-loaded with purpose. Every sentence contributes to understanding the tool's core functionality.

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?

Given 4 parameters, no output schema, and no annotations, the description is too sparse. It omits return values, error conditions, and prerequisites for a tool with significant effects (restore).

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 0%, so description must add meaning. It only references 'confirm' and 'dryRun' indirectly, ignoring 'app' and 'backupFile'. This provides little value beyond the schema itself.

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 it's for planning or restoring a backup, distinguishing it from siblings like 'create_backup' and 'list_backups'. It identifies two operational modes, which is specific, but could be more explicit about what 'plan' entails.

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?

It provides clear parameter conditions for actual restore ('confirm true and dryRun false'), implicitly guiding when to plan vs restore. However, it lacks guidance on prerequisites or when not to use the tool.

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