as_restore_backup

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description adds value by specifying the confirm requirement and the automatic backup of the current destination, providing behavioral context beyond 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 concise and well-structured: a one-sentence summary followed by an Args section and a Returns line. No redundant information.

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?

The description covers the essential behavioral details (confirm requirement, backup of destination), the return type (JSON string), and the parameters. With output schema and annotations present, the description is sufficiently complete.

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 description lists the three arguments (backup_path, restore_to, confirm) but adds minimal meaning beyond the input schema, which already provides descriptions for each. Schema description coverage is reported as 0%, but the schema itself includes descriptions for the nested RestoreInput properties.

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 'Restore a previously-created backup file to a destination.' It uses a specific verb ('Restore') and resource ('backup file'), and distinguishes itself from sibling tools like as_backup_file and as_project_backup.

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 mentions that 'confirm=true' is required and that the current destination is backed up before overwriting, providing clear context. However, it does not explicitly state when to use this tool over alternatives or list any exclusions.

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