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

No annotations are provided, so the description carries the full behavioral burden. It adds important transactional context (cost, payment rail) and names restart/port-conflict repair actions, but it does not disclose side effects such as whether restarts are disruptive, what permissions are needed, or how the fix is applied. This is useful context but not a complete safety/behavior profile.

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 tight sentences: the first says what it does, the second says when to use it, the third adds the exclusion and cost. Every sentence earns its place, and the most important routing information is front-loaded.

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 complexity and the lack of annotations and output schema, the description covers purpose, usage, exclusions, and cost well. It does not describe what the tool returns or what diagnostics/actions the agent should expect, which is a minor gap for a fix-oriented tool with no output schema.

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?

There is one parameter with 100% schema description coverage, so the schema already documents the query field. The description adds no syntax or format guidance beyond that, which matches the baseline of 3 when schema coverage is high and the description does not compensate with extra meaning.

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 and resource: 'Fix ComfyUI operations issues on a remote Linux/DGX Spark host,' then enumerates concrete sub-areas (process detection, restarts, port conflicts, SSH quirks). It also explicitly distinguishes itself from the sibling fix_comfyui_api_prompt_error, so an agent can select it without ambiguity.

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 states exactly when to use the tool ('ComfyUI is down, wedged, duplicated, or unreachable') and when not to use it ('Do NOT use for workflow/node errors — that's fix_comfyui_api_prompt_error'). This is explicit routing with both positive and negative conditions and a named alternative.

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