restart_comfyui

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

Discloses key behaviors: stopping with config capture, port freeing, relaunch with same args, and bounded readiness polling. No side effects or permissions mentioned, but sufficient for a restart action.

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?

Single sentence that is front-loaded with the verb 'Restart' and efficiently details the process in a colon-separated list. No wasted 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?

Missing output/return value description, which is important for an action tool. Otherwise covers the process adequately.

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?

No parameters exist, so description provides relevant high-level behavior. Baseline 4 applies as per guidelines for zero-parameter tools.

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?

Description clearly states it restarts ComfyUI with a specific sequence of actions, distinguishing it from start_comfyui and stop_comfyui by combining both operations with readiness polling.

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 explicit guidance on when to use this tool versus start_comfyui or stop_comfyui. Context implies it's for full restart, but lacks direct comparison or exclusion statements.

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