comfy_cli_search_nodes

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

With no annotations, the description carries full burden. Discloses it uses official command and modes (local/cloud/offline). Does not detail authorization, rate limits, or behavior on invalid input.

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 concise sentences with zero waste. Every sentence adds value: purpose, sibling differentiation, and usage modes.

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?

High-level purpose and usage modes are covered, but parameter details (limit, workspace, objectInfoPath) are missing. No output schema or annotations. Adequate for a simple search tool but not fully comprehensive.

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 low (20%). Description only mentions query and hints at where. Limit, workspace, objectInfoPath are not explained beyond schema defaults. Does not compensate for the gap.

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 it fuzzy-searches ComfyUI node classes by name/display/description using official `comfy nodes search`. Explicitly distinguishes from sibling `search_custom_nodes` which searches installable node packs.

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?

Explains complement to search_custom_nodes and mentions it works locally, in cloud, or offline. Provides context for when to use, but lacks explicit when-not-to-use or prerequisites.

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