restore_snapshot

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

No annotations are provided, so the description carries the full burden. It discloses destructive behavior: 'queries created since are deleted' and explains the 'latest' default behavior. This is meaningful behavioral context beyond the schema. It could add more about reversibility or side effects, but the core destructive nature is disclosed.

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 compact and front-loaded with the main action. The parenthetical about `queries` and the 'latest' note are useful and placed efficiently. It earns its place without excessive detail.

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 tool has 4 parameters, no output schema, and no annotations. The description covers the core behavior and two parameters, but leaves `source` and `dry_run` unexplained. For a destructive operation, the missing `dry_run` semantics and the required `source` parameter are notable gaps.

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 description coverage is 0%, so the description must compensate. It explains `queries` (partial restore) and `snapshot_id` ('latest' undoes the most recent write), but does not explain `source` or `dry_run`. The description adds value for two of four parameters, but leaves the required `source` and the safety-relevant `dry_run` undocumented.

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 action ('Roll back to a snapshot') and the resource (snapshot/query set), and distinguishes the partial vs full restore behavior. It doesn't explicitly name sibling tools like list_snapshots or copy_queries, but the verb 'restore' plus the rollback semantics make the purpose clear.

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 the tool: to roll back to a snapshot, with a conditional for partial restore via `queries` vs full restore. It doesn't explicitly state when not to use it or name alternatives, but the context is clear enough for an agent to select it over list_snapshots or copy_queries.

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