restore_db

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

With no annotations, the description fully discloses destructive behavior: overwrites live database, renames old copy with timestamp, requires restart, returns status. All critical behavioral traits are explained.

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?

Concise and well-structured: one-sentence purpose, safety note, important warnings, then parameter list. Every sentence adds essential information; 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?

Covers all key aspects for a destructive restore tool: safety mechanism, prerequisites (confirmation), post-action requirement (restart), and return format. Output schema existence is noted. Complete given the complexity.

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%, yet the description clearly defines backup_path as 'Full path to the .sqlite backup' and confirm as 'Must be the string 'YES' to proceed,' adding meaning absent from 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?

The description opens with 'Restore the Metis database from a backup,' clearly stating the verb and resource. It distinguishes from siblings like backup_db by focusing on restoration and the overwrite behavior.

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 context: overwrites live database, loss of changes since backup, required restart, and the rename safety mechanism. Does not explicitly contrast with backup_db, but the purpose and warnings strongly guide appropriate use.

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