comfyui_restart

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

The description discloses the sequence of operations (stop, flush, start), which adds behavioral context. However, it does not mention potential side effects like loss of unsaved state or authentication requirements. With no annotations, more detail would be beneficial.

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 very short (one sentence) and front-loaded, but it omits essential information about parameters. Conciseness is good, but at the cost of completeness.

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 the restart action, two parameters, and no output schema, the description is incomplete. It lacks details on parameter effects, return values, and prerequisites (e.g., whether ComfyUI must be running).

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 description coverage is 0%, yet the description completely ignores the two boolean parameters (lowvram, novram). It provides no explanation of how these affect the restart behavior, leaving the agent uninformed.

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 restarts ComfyUI with specific actions: stop, flush VRAM, start fresh with GPU optimizer. This distinguishes it from sibling tools like comfyui_stop, comfyui_start, vram_flush, and gpu_optimize.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't specify scenarios where a full restart is preferred over separate stop/start or plain optimization.

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