comfy_restore_snapshot

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

No annotations are provided for this tooliones. The description says 'Get a snapshot's workflow data' and 'Returns: JSON with full snapshot data including workflow', which implies a read operation, but it does not disclose whether restoration has side effects, requires specific permissions, or modifies system state. The tool name suggests 'restore' (implying a write), while the description says 'Get' (implying a read) — this ambiguity is not resolved.

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 concise: one clear line on purpose, one on args, one on returns. No wasted words or 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?

With no annotations providedholistically, the description must disclose all behavioral traits. It fails to clarify the nature of 'restore' — does it apply the snapshot or just fetch it? The return is said to include 'full snapshot data including workflow', which implies it's for retrieval, not execution. Yet tool name 'restore_snapshot' (though this is comfy_restore_snapshot) suggests a write operation. It doesn't mention permissions, side effects, or how the returned data is meant to be used. For a tool likely involved in workflow restoration, this is 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?

Only one parameter (snapshot_id) is defined, and the description states 'The snapshot ID to restore' plus the return includes workflow data. However, the description lacks details about the ID format, how to obtain it (likely from other snapshot tools), and any additional constraints. Since there's only one parameter and the description covers its purpose, this is adequate but not thorough.

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 gets a snapshot's workflow data for restoration, using a specific verb ('Get') and resource ('snapshot'). It differentiates from sibling tools like comfy_snapshot_workflow (which creates snapshots) and comfy_list_snapshots (which lists them), though it doesn't explicitly name these alternatives.

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 implies when to use this tool (when you need snapshot's workflow data for restoration) but does not explicitly state when not to use it or mention alternatives like comfy_list_snapshots or comfy_diff_snapshots. The 'for restoration' context gives some usage direction but lacks explicit exclusions.

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