restore_node_snapshot

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

No annotations exist, so the description bears full burden. It discloses the key behavior that changes are applied on next restart, which is critical for understanding the tool's effect. Does not mention destructive potential or permissions, but the restart cue implies a significant state change.

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 two concise sentences, front-loading the core action and CLI equivalence, then adding behavioral and contextual notes. Every word earns its place with no redundancy.

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?

For a single-parameter tool with no output schema, the description covers the purpose, prerequisite (list_node_snapshots), and side effect (restart needed). It omits error scenarios or success indicators, but the complexity is low enough that this is acceptable.

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?

With 100% schema coverage, the baseline is 3. The description adds 'as shown by list_node_snapshots' to the name parameter, reinforcing the schema's description but not providing new structural or format details beyond what the schema already conveys.

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 ('Restore a previously saved custom-node snapshot') and the resource ('custom-node snapshot'), and distinguishes from sibling tools like save_node_snapshot and list_node_snapshots by using a specific verb and referencing the CLI equivalent.

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?

Provides explicit guidance on using list_node_snapshots to find available snapshot names and notes that changes apply on next restart, offering context for when to use the tool. Could be improved by stating when not to use (e.g., if running jobs), but sufficient for typical scenarios.

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