comfyui_download_model

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

Annotations indicate this is not read-only and is open-world, but the description adds valuable behavioral context by stating that the tool returns a 'JSON with download task status' and that progress should be checked via another tool. This implies an asynchronous task model, which is important beyond the raw annotation flags.

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 two short, front-loaded sentences. The first sentence states the core purpose and mechanism; the second explains the return value and next step. No wasted words.

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 the output schema exists and parameter schema is fully covered, the description does not need to repeat those details. It provides enough context: what the tool does, what it returns, and how to follow up. This is complete for an agent to invoke the tool correctly.

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?

The input schema already provides 100% coverage of parameters, so the baseline is 3. The description adds meaning by naming HuggingFace and CivitAI, which clarifies the 'allowed domain' constraint on the 'url' parameter and gives the agent a better sense of valid inputs.

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 action ('Download a model'), the specific sources ('from HuggingFace or CivitAI'), and the mechanism ('via ComfyUI-Model-Manager'). This distinguishes it from sibling tools like comfyui_search_models or comfyui_get_download_tasks.

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 provides clear context for when to use the tool (to download models) and gives a direct follow-up instruction ('Use comfyui_get_download_tasks to check progress'). It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to select it appropriately.

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