snapshot_restore

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

The annotations already mark the tool as destructive and non-read-only, but the description adds valuable safety behavior: overwriting current contents, requiring an exact confirm_name match, being blocked in read-only mode, and requiring explicit user confirmation. This is strong behavioral disclosure beyond annotations.

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 crisp sentences with no filler. The destructive warning and confirmation condition are foregrounded, and each sentence adds meaningful information.

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?

With an output schema available and annotations covering read-only and destructive hints, the description supplies the remaining operational context: overwrite behavior, confirmation requirement, and read-only blocking. An agent has enough to invoke this safely.

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 carry the parameter semantics burden. It explains confirm_name's exact-match requirement and the collection target, and snapshot_name is implied as the previously created snapshot. All three required parameters are inferable, though not formally parameter-by-parameter documented.

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?

Clearly states the action: restore a collection from a previously created snapshot and overwrite current contents. It is distinct from snapshot_create and collection_delete based on this description alone.

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?

States a clear guardrail: only use when the user has explicitly confirmed the overwrite. It also says read-only mode blocks the operation. It does not name contrasting use cases such as when snapshot_create or collection_delete would be more appropriate, so it falls just short of full explicit alternative guidance.

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