reload_comfyui

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

With no annotations, the description carries the behavioral burden and does disclose the critical side effect: it kills the process on the ComfyUI port and starts main.py from COMFYUI_PATH. It also covers required environment variables and post-restart sync behavior, but does not mention downtime, running-workflow interruption, or failure behavior.

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 front-loaded with the core action and is generally efficient. The sync behavior is mentioned twice, once in the opening and again in the final sentence, which is slightly redundant but not harmful.

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?

For a restart tool with no annotations and no output schema, the description is substantially complete: it covers prerequisites, the destructive process action, and the follow-up sync path. It could be stronger by noting the impact on running jobs or expected return behavior, but the critical context is present.

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 100%, so the three parameters are already documented in the schema. The description adds only a brief mention that sync_after_restart can be set to true; it does not materially explain wait_for_ready or wait_timeout_ms beyond what the schema provides.

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 states a specific verb and resource: restart ComfyUI so newly installed custom nodes are loaded. It also distinguishes the related sync step by naming sync_nodes_to_knowledge and the sync_after_restart option, so an agent can tell it apart from the sync and plugin-reload siblings.

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 says when to use the tool: after custom nodes are installed and need to be loaded. It also points to sync_nodes_to_knowledge after restart or the sync_after_restart parameter, though it does not explicitly contrast itself with reload_plugins or state when a restart should be avoided.

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