node_snapshot

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

With no annotations, the description carries the full behavioral burden. It discloses the read-only nature of list, write behavior for save, the requirement for local install for named saves (unavailable on remote), and that restore applies on next restart. This is thorough and actionable.

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 uses a well-structured bullet format to cover three actions. Each sentence provides essential information, and the length is appropriate for the tool's complexity without 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?

Despite lacking output schema and annotations, the description comprehensively covers the tool's operations, constraints, and dependencies (e.g., workspace tool). It leaves little ambiguity about invocation or behavioral expectations.

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%, but the description adds meaningful semantics beyond the schema: it explains how `action` drives behavior and clarifies `name` optionality/requirement depending on the action, plus remote/local caveats. This goes well beyond the baseline.

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 identifies the tool as managing custom-node snapshots via ComfyUI-Manager and enumerates three specific actions (list/save/restore). This distinguishes it from sibling tools like install_custom_node and node_pack.

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 provides per-action usage scenarios, including when to omit name for timestamp-named saves, and when a name requires a local install root. It explicitly points to the workspace tool for a prerequisite, giving concrete guidance for when to use each action.

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