download_model

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

With no annotations provided, the description carries the full burden. It clearly states the destination directory and acceptable URL sources. However, it does not disclose whether existing files are overwritten, or any permissions or size limitations, which would be useful for a download operation.

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?

Single sentence that is front-loaded with the core action and destination. No wasted words. Very concise.

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 tool's relative simplicity, the description covers the main context. There is no output schema, so return values are not explained, but that is acceptable. One could argue for mentioning success/error feedback, but overall it is sufficiently complete.

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 description coverage is 100%, so baseline is 3. The description adds value by clarifying that the url is a direct download link, that filename auto-detects from URL if omitted, and that target_subfolder is an enum with examples like 'checkpoints', 'loras', etc. This provides meaning beyond the schema.

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?

Description explicitly states the tool downloads a model file to the ComfyUI models directory from a URL, mentioning both HuggingFace and direct links. This clearly distinguishes it from sibling tools like list_local_models or search_models.

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 implies usage for downloading models from specific URL types but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. Sibling tools like search_models or list_local_models exist, but no comparative guidance is given.

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