restore_node_snapshot

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

The description reveals that changes are applied on the next ComfyUI restart, a critical behavioral detail. Since no annotations are provided, the description carries the full burden and meets it well. A slightly higher score could be justified with more detail, but 4 is appropriate.

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?

Two concise sentences, each serving a purpose: first defines the action and method, second provides crucial behavioral and usage context. No unnecessary 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?

For a simple tool with one parameter and no output schema, the description covers purpose, usage prerequisite, a critical behavioral side effect, and a CLI equivalent. It is fully sufficient for an agent to select and invoke the tool correctly.

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?

The single parameter 'name' is described in the schema as 'Name of the snapshot to restore (as shown by list_node_snapshots).' The description repeats this verbatim, adding no extra meaning. With 100% schema coverage, a baseline of 3 is correct.

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's action ('Restore'), the resource ('previously saved custom-node snapshot'), and the method ('via ComfyUI-Manager'). It explicitly references the sibling tool list_node_snapshots, distinguishing it from related tools.

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 instructs to use list_node_snapshots to find available snapshot names, providing a clear prerequisite. While it doesn't explicitly state when not to use the tool, the context and sibling tools imply alternatives. A score of 4 reflects good guidance with minor room for improvement.

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