comfy_refresh_models

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description discloses that it re-reads the current cache and explicitly states it does NOT trigger a server-side rescan, which is critical behavioral nuance. It also clarifies the return format (per-folder counts), adding transparency not covered by annotations.

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 compact: a single clear sentence for purpose followed by a concise note on behavior and return value. Every sentence contributes meaningful information without fluff, and it is front-loaded with the primary action.

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 a tool with no parameters, the description is complete: it states what it does, what it does not do (filesystem rescan), and what it returns (per-folder counts). The presence of an output schema and annotations further supplements the context, so nothing essential is missing.

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?

With zero parameters, the description does not need to explain any. According to the rubric, a 0-parameter tool receives a baseline of 4. The description adds no unnecessary parameter info, so it maintains this baseline.

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 states a specific action: 'Re-fetch the model list from ComfyUI across every known folder.' It clearly identifies the resource (model list) and scope (every known folder), distinguishing it from listing tools like comfy_list_models by emphasizing it's a refresh operation. The mention of returning per-folder counts adds further specificity.

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 note explains that it re-reads the cache and does NOT trigger a filesystem rescan, which informs when to use it (to refresh cached data) and when not to (if a rescan is needed). However, it does not explicitly reference alternative tools like comfy_list_models for listing, leaving some ambiguity about when to choose this over them.

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