install_model

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

With no annotations, the description carries the full burden. It usefully discloses the COMFYUI_PATH dependency and comfy-cli fallback, but it omits important install behaviors such as overwrite handling, authentication requirements, disk write effects, and failure modes.

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 front-loaded and efficient, explaining the core action, prerequisite, and fallback mechanism without excessive prose. The final model_type list is somewhat redundant with the schema, keeping it from a 5.

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?

For an install/mutation tool with no annotations and no output schema, the description covers the main mechanism but is incomplete on side effects and expected outcomes. An agent still lacks guidance on overwrite behavior, return values, and failure handling.

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 the schema already documents both parameters. The description repeats the model_type values but adds no extra meaning beyond the schema, so the baseline score of 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 gives a specific verb+resource: download and install a model by URL. It also enumerates model types, making it clearly distinct from sibling tools like list_models, get_model_info, and check_model_exists.

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?

It provides prerequisite context (COMFYUI_PATH) and implementation behavior (comfy-cli fallback), but it does not explicitly say when to use this instead of checking existence first or when not to use it.

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