update_all

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

No annotations provided, so description carries full burden. Discloses queuing behavior, worker start, async execution, and restart requirement. Lacks detail on safety (e.g., idempotency) but overall good coverage of behavioral traits.

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 concise sentences with front-loaded action. First sentence states core function, second clarifies scope, third adds context. No redundant words.

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 no parameters and no output schema, description covers action, scope, mechanism, async nature, and post-requirement (restart). Sufficient for agent to decide invocation.

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?

Input schema has zero parameters. Description adds no parameter info (unnecessary). Baseline score for 0 parameters is 4, and the description appropriately omits parameter 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?

The description clearly states the tool updates all installed custom nodes, distinguishes from ComfyUI core updates, and uses specific verb 'update' with resource 'ALL installed custom nodes'. It explicitly differentiates from sibling 'update_comfyui'.

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?

Provides clear when-to-use (bulk update of custom nodes) and when-not (for core, use update_comfyui). Mentions async behavior and potential restart. Does not explicitly mention alternative 'update_custom_node' for selective updates, but context is sufficient.

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