comfy_cli_server

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

No annotations are provided, so the description must convey behavioral traits. It explains that restart performs 'comfy stop' followed by 'comfy launch --background', which is transparent. However, it does not discuss prerequisites, side effects, or error conditions for start/stop actions.

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, front-loading the core purpose and actions. It is concise, with no wasted words, and every sentence adds value.

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 management tool with 3 parameters and no output schema, the description provides sufficient context to understand usage. However, it lacks differentiation from similar sibling tools (start_comfyui, stop_comfyui) and does not describe return values or success indicators.

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 67%, so baseline is 3. The description adds context for the 'restart' action but otherwise repeats schema information for parameters 'workspace' and 'launchArgs'. It provides limited additional meaning beyond the schema.

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 the tool's purpose clearly: start, stop, or restart a local ComfyUI via comfy-cli. It distinguishes from siblings by mentioning specific actions and referencing comfy_cli_status for inspection, making it specific and actionable.

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 description gives guidance on using comfy_cli_status for inspection, providing context for when not to use this tool. However, it does not explicitly differentiate from similar-named siblings like start_comfyui and stop_comfyui, which could cause confusion.

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