restore_db

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

With no annotations provided, the description fully discloses the renaming of the current database to a timestamped backup, the overwrite action, loss of changes, and the need to restart the dashboard. It also notes the return format, providing complete behavioral transparency.

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 well-structured: a clear purpose sentence, step-by-step explanation, important warnings, and parameter descriptions. It is concise with no unnecessary information, every sentence serves a purpose.

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 the complexity of a restore operation with a safety rename, the description covers the process, the confirm parameter, the implications of overwriting, and the need for dashboard restart. An output schema exists but the description already mentions the return format, making it complete enough for an AI agent to use 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 input schema has no parameter descriptions (0% coverage). The description compensates by explaining that backup_path is a full path to a .sqlite file and confirm must be the string 'YES'. This adds essential meaning beyond the raw 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 clearly states 'Restore the Metis database from a backup' using a specific verb and resource. It explains the renaming behavior and distinguishes the tool from siblings like backup_db and verify_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 warns that the operation overwrites the live database and requires a dashboard restart, implying when to use. However, it does not explicitly state when not to use or mention alternatives, leaving room for clearer guidance.

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