search_custom_nodes

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

No annotations provided, so description carries full burden. Clearly states 'Read-only and network-only' and 'does NOT require a running ComfyUI or COMFYUI_PATH,' disclosing safety and network dependency. Does not detail rate limits or exact response structure beyond fields, but sufficient for a search tool.

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?

Single cohesive paragraph with front-loaded action and key constraints. Every sentence adds value: purpose, network dependency, return fields, sibling differentiation, and follow-up action. No redundant or vague language.

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 3 parameters, no output schema, and no annotations, the description covers all essential context: what it searches, how it works (HTTP to registry), what it returns (list with fields), what it does not do (models, local installs), and how to use results. Comprehensive for the tool's complexity.

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 coverage is 100%, so baseline is 3. Description adds context for 'query' (keyword match against name/description) and mentions default limit of 10. Also explains how returned id is used (pass to get_node_pack_details). This adds meaningful usage context beyond schema descriptions.

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 'Search the public ComfyUI Registry for custom node packs by keyword,' specifying the action, exact resource (registry.comfy.org), and scope. Distinguishes from siblings like search_models and list_local_models, which are explicitly mentioned as what this tool does NOT do.

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 explicit guidance: use to discover packs to install, pass returned id to get_node_pack_details for full info. Also states when not to use (does not require running ComfyUI or COMFYUI_PATH) and differentiates from search_models and list_local_models. Includes network-only and read-only constraints.

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