search_custom_nodes

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

With no annotations provided, the description fully discloses behavior: read-only, network-only, no need for running ComfyUI or COMFYUI_PATH, and returns a ranked list with specified fields. It is transparent about its non-destructive nature and network dependency.

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?

The description is five sentences, front-loaded with purpose, followed by constraints, usage hints, and sibling differentiation. Every sentence adds value, and there is no redundant or vague phrasing.

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?

The tool is simple with three parameters and no output schema. The description covers the return structure (ranked list with fields) and how to use the results. It provides sufficient context for an agent to understand inputs, behavior, and output without needing additional information.

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. The description does not add significant detail beyond the schema for the query, limit, and page parameters. It mentions the query matches pack name/description, but this is already implied. No extra constraints or format guidance are provided, so it neither improves nor worsens the baseline.

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 searches the public ComfyUI Registry for custom node packs by keyword. It specifies the registry URL and distinguishes from siblings like search_models and list_local_models, leaving no ambiguity about what it does.

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?

The description explicitly says to use the tool for discovering packs to install and to pass a returned id to get_node_pack_details. It also clarifies what it does not search (models and local installs) and directs to alternative tools, providing excellent usage guidance.

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