comfy_stop

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

With no annotations, the description carries the full burden of behavioral disclosure. It accurately states the action and its limitation (only stops the server-started process), which is the key behavioral nuance. It could mention side effects or edge cases, but for a simple process-stop tool, this is adequately 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 two short sentences, front-loaded with the main action. Every word earns its place, and the second sentence adds a necessary scope clarification. No waste.

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?

Given the tool's simplicity (no parameters, an output schema exists, siblings provide surrounding context), the description is complete enough. It could briefly mention results or relation to comfy_start, but for a stop command the scope statement is the key missing piece, and that is provided.

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?

The tool has zero parameters, so per the rubric the baseline is 4. The description adds no parameter details because none exist, which is appropriate. There is nothing more to explain.

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 uses a specific verb ('Stop') with a clear resource ('the ComfyUI process that this server started'), which immediately distinguishes it from siblings like comfy_start and restart_comfy. The additional clause about not touching self-launched ComfyUI further clarifies scope.

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 clearly indicates when to use this tool: to stop the server-managed ComfyUI process. It also provides an implicit exclusion ('A ComfyUI you launched yourself is not touched'), signaling when not to rely on it. It does not mention alternatives explicitly, but the context is sufficient for a simple stop action.

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