download_civitai_model

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

With no annotations, the description fully bears the transparency burden. It discloses the resolution via REST API, streaming to disk, subfolder writing, and error condition when COMFYUI_PATH is unset. It does not mention rate limits or overwrite behavior, but covers critical behaviors adequately.

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 concise and well-structured. Four sentences front-load the purpose and then detail resolution process, local-only constraint, and authentication requirement. Every sentence adds necessary information without redundancy.

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 scope (download a file), the description covers inputs, resolution, output (absolute path), error conditions (unset COMFYUI_PATH), and authentication. No output schema exists, but the return value is clearly stated. Comprehensive for the task.

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% so baseline is 3. The description adds semantics by explaining the relationship between model_id and model_version_id (latest version vs specific version) and the requirement to provide at least one. This goes beyond the schema's individual descriptions.

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's purpose: downloading a model from CivitAI to the local ComfyUI models/ directory and returning the absolute path. It distinguishes from siblings like 'download_model' by specifying CivitAI-specific resolution and local-only behavior.

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?

Provides explicit context: requires at least one of model_id or model_version_id, notes local-only restriction, and warns about gated models needing CIVITAI_API_TOKEN. However, it does not directly compare to alternative tools like 'download_model' or specify when not to use this tool.

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