restore_snapshot

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

Annotations declare destructiveHint=true, and the description adds context: 'Current project state will be overwritten' and 'Async operation', which are beyond annotations. It does not contradict annotations and provides useful behavioral details.

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 sentences front-load purpose and destructiveness, then add dryRun and async details. Efficient but could be slightly more concise by combining sentences, hence not a 5.

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 no output schema, the description misses the return value (likely a task id for async operation) and prerequisites like snapshot existence or permissions. For a destructive async tool with 4 params, it is adequate but incomplete.

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 100% with descriptive parameter comments. The description highlights dryRun but adds no new parameter-specific meaning beyond the schema, achieving the baseline of 3.

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 verb ('Restores') and resource ('snapshot to its Cognigy.AI project'), and the phrase 'replacing the current configuration' distinguishes it from sibling tools like list_snapshots or create_snapshot which do not modify project state.

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 explicitly advises using dryRun=true for validation first, which guides safe usage. However, it does not provide explicit when-not-to-use or mention alternatives like get_snapshot for inspection, leaving some room for misinterpretation.

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