update_custom_node

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

Discloses the fallback mechanism and use of HTTP API or subprocess. However, no annotations are present, so the description carries full burden; it does not mention side effects, requirements like permissions, or error behavior.

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?

Two efficient sentences. First sentence expresses purpose, second explains mechanism. No unnecessary 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?

Lacks output schema description and prerequisites (e.g., ComfyUI must be running, manager installed). Given no output schema, the description should clarify return values or success indications.

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 description coverage is 100%, so each parameter is documented. The main description adds context about the overall behavior but does not significantly enhance parameter understanding beyond 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?

Clearly states the verb 'update' and resource 'custom node pack', including the special 'all' option. Differentiates from siblings like install_custom_node, reinstall_custom_node, and update_all.

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 context for when to use (to update a pack or all packs) and the mechanism (HTTP API with fallback). Lacks explicit when-not-to-use or alternatives, but the context is clear enough.

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