restart_comfyui

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

With no annotations, the description carries full burden. It discloses the stop-then-launch sequence, extra_args forwarding, confirmation prompts, kill behavior, concurrency refusal, and remote target skip. This is exceptionally transparent.

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 detailed but each sentence adds a distinct behavioral fact. It is front-loaded with the composed operation and then covers edge cases. No redundancy or fluff.

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?

Covers purpose, error handling, concurrency, network exposure, untracked port, parameters, and return status. For a tool with no annotations and no output schema, this is complete and leaves nothing an agent needs to call it 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?

Schema coverage is 0%, but the description explains all three parameters: extra_args forward to the new server, confirm_network_exposure is the no-prompt fallback, and confirm_kill_untracked defaults to False and kills nothing. Fully compensates for the schema gap.

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 the LOCAL ComfyUI server and explicitly composes stop_comfyui + launch_comfyui, distinguishing it from sibling tools. The verb-resource pair is specific and unambiguous.

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?

It explains the composition and mentions the network-exposure confirmation and untracked port handling, but does not explicitly name when to prefer this over the siblings (e.g., 'use launch_comfyui for a fresh start'). However, the composition statement makes the intended use obvious, so this is clear enough.

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