stop_comfyui

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

Discloses key behaviors: captures process info, kills process tree, resets WebSocket client. Without annotations, this is good, though could mention safety or side effects like unsaved work.

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?

Three sentences, front-loaded with main purpose, each sentence adds value. No redundancy.

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 0-parameter stop function with no output schema, the description fully addresses what the tool does and its relationship to start_comfyui.

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, so description doesn't need to add meaning. Baseline 4 is appropriate as it covers purpose without needing param details.

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?

Clearly states the verb 'Stop' and the target resource 'ComfyUI process'. Differentiates from siblings like restart_comfyui and start_comfyui by highlighting process info capture for restart.

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?

Explicitly mentions pairing with start_comfyui for restart, implying when to use. Does not explicitly exclude alternatives like restart, but context with siblings makes it clear.

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