comfy_cli_models

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

No annotations are provided, so the description must fully disclose behavioral traits. While it mentions discover, download, and remove, it lacks details on side effects (e.g., whether download overwrites, if remove is permanent, if authentication is needed). The description does not cover the full range of actions or their consequences.

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 a single concise sentence, but it is too brief for a tool with 11 parameters and 6 actions. It front-loads 'Discover model folders/files' but does not structure the information for clarity or mention all actions. While not verbose, it lacks necessary detail.

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 complexity (11 parameters, 6 actions, many sibling tools, no output schema), the description is incomplete. It omits the action parameter explanation, parameter-action dependencies, and does not convey the full scope of operations. An agent would likely misuse or underutilize this tool.

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?

Only 3 out of 11 parameters have schema descriptions, and the tool's description does not add meaningful information about the parameters. It fails to explain how parameters relate to actions (e.g., which parameters are required for download vs. remove) or provide usage context for the many enum values.

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 three main operations (discover, download, remove) and identifies the resource (model folders/files). However, it does not mention the other actions available (list-folders, list-folder, search, show) and fails to differentiate from sibling tools like search_models, download_model, remove_model.

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 no guidance on when to use this tool versus alternative sibling tools that perform similar operations, such as search_models, download_model, or remove_model. An agent has no context to choose the appropriate tool.

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