Restore SaveData

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is structured. The description adds genuinely useful context beyond that: the current file is auto-backed-up first and the backup is named 'pre-restore-*', which materially softens the destructive operation and tells the agent a recovery path exists.

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?

A single compact sentence with a parenthetical, front-loading the list/restore duality and the auto-backup detail. Every clause carries information with no filler.

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 tool whose annotations carry the destructive/readOnly profile and with no output schema, the description covers the essentials plus the auto-backup behavior. It stops short of describing the return format of the listing or restore result, but is otherwise 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?

Schema coverage is 100%, and the schema's own description ('Backup filename from the list, or empty to list') already documents the single parameter. The description's param hint ('Omit backup to just list') largely restates that, so the baseline of 3 is appropriate.

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+resource ('restore one' / 'List Backups/') and its dual nature clearly, so an agent knows it both enumerates backups and restores them. It does not explicitly distinguish itself from the close sibling reanim_backup_savedata, but the restore-vs-backup verb distinction is inferable.

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?

'Omit backup to just list' gives an explicit condition that selects between the two modes of this tool. It does not name or exclude sibling tools (e.g., reanim_get_savedata or reanim_backup_savedata), so the routing guidance is clear but not exhaustive.

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