search_models

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

Discloses read-only and network-only behavior, no need for ComfyUI or COMFYUI_PATH, and no downloads. No annotations provided, so description fully carries the burden.

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 sentences: purpose, behavior, usage guidance. Front-loaded and concise with no extraneous information.

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?

Covers search scope, return fields (modelId, author, downloads, likes, tags), and downstream workflow (pass to download_model). No output schema, but return info is sufficient.

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% with descriptions for all 3 parameters. Description adds no extra parameter information beyond schema, so baseline 3 is appropriate.

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 HuggingFace Hub for models usable in ComfyUI, listing specific types (checkpoints, LoRAs, VAEs, ControlNets). It distinguishes from siblings like search_civitai_models and search_custom_nodes.

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?

Explicit guidance on when to use this tool versus alternatives: For CivitAI searches, use search_civitai_models; for custom nodes, use search_custom_nodes. Also links to download_model for installing results.

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