search_models

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

Fully discloses read-only and network-only nature, that it queries HuggingFace over HTTP, does not download, and returns specific fields. No annotations present so description carries full burden and meets it well.

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?

Concise at 5 sentences, front-loaded with purpose, then constraints, output info, and usage guidance. No superfluous content.

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?

No output schema, yet description explains return fields (modelId, author, downloads, likes, tags) and ties to subsequent download_model tool. Complete for a search tool with 3 params.

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 adequate descriptions. The description adds context about model types and return fields but does not significantly enhance parameter meaning beyond what the schema already provides.

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?

Clear verb ('Search') and specific resource ('HuggingFace Hub for models usable in ComfyUI'). Lists model types and distinguishes from sibling tools like download_model 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?

Explicitly states when to use (searching for models) and when not (use search_custom_nodes for custom nodes). Also clarifies it does not require ComfyUI or download anything.

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