Restore Database

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

Annotations indicate destructiveHint: true and idempotentHint: true. The description adds context: it verifies backup integrity before replacing the live database and requires a server restart. This adds value beyond annotations without contradiction.

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?

Three concise sentences, front-loaded with purpose. Every sentence adds necessary information: operation, verification, and post-restart requirement. No extraneous words.

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 destructive nature and restart requirement, the description provides essential context. It could mention response_format behavior, but with output schema present, this is a minor gap. Overall it is adequate for agent invocation.

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?

Input schema has 2 parameters with 50% description coverage. The description clarifies the source parameter as a 'backup .db file', but does not elaborate on response_format. The output schema exists, so return value info is not required. Schema does most of the work; description adds some value.

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 the tool restores the LocalNest memory database from a backup file, using a specific verb ('Restore') and resource ('memory database'). It distinguishes itself from siblings like localnest_backup by describing a distinct operation (restoring vs. backing up).

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 explains when to use this tool (to restore from a backup) and mentions a critical post-condition (server restart). However, it does not explicitly state when not to use it or compare to alternatives like localnest_backup. Clear context but missing exclusions.

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