Connect ComfyUI

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

The description discloses key behavioral details beyond the annotations: the fallback logic between tox_drop and webclient modes, and the exposed Null TOP output. It adds useful context about what the tool does internally, though it omits potential side effects like overwriting existing components or network-level changes.

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 two sentences long and front-loaded with the primary action and outcome. Every phrase earns its place without redundancy, making it concise and well-structured.

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?

With 13 parameters and no output schema, the description provides a high-level overview but does not fully explain the workflow, prerequisites, or failure modes of the webclient path. The schema supplements this, but the tool description alone feels incomplete for such a complex tool.

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%, so the baseline is 3. The description references the mode and output behavior (tox drop, webclient, Null TOP) but does not add parameter-level meaning beyond the already thorough schema descriptions. The schema carries the semantic load.

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's purpose: to bridge a running ComfyUI server. It specifies the two distinct approaches (dropping TDComfyUI .tox or building a stock webclientDAT skeleton) and the resulting output (Null TOP at <container>/out), which distinguishes it from other connection tools like connect_a1111_webui_bridge.

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 context is clear (for connecting to a running ComfyUI server), but the description does not explicitly say when to use this tool over alternatives, nor does it provide exclusions or prerequisites. The guidance is implied by the tool's name and opening phrase, not explicitly addressed.

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