resolve_missing_models

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

No annotations are provided, so the description carries full burden. It discloses read-only behavior, detection mechanism (comparison against server option list), and the information reported for each candidate (size, source, precision, VRAM fit). This fully covers behavioral traits.

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 comprehensive and well-structured, front-loading the main purpose. While slightly lengthy, every sentence adds necessary information, such as detection scope, candidate details, and cross-references to sibling tools.

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 no output schema, the description thoroughly explains what the tool returns (candidates with size, source, precision, VRAM fit) and how it works. It also contextualizes within the broader tool ecosystem, covering all necessary information for an AI agent to select and invoke correctly.

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%, providing baseline of 3. The description adds value by clarifying that the workflow parameter expects 'ComfyUI workflow in API format (JSON string or object)', adding context beyond the schema property 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 it finds missing model files for a ComfyUI workflow and searches CivitAI and HuggingFace for candidates. It specifies the verb 'find' and 'search', resource 'model files', and distinguishes from sibling tools like download_model and install_workflow_dependencies.

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?

Explicitly states it is 'THE tool' for missing models, notes it is read-only, and directs to use download_model or download_civitai_model for downloading, and install_workflow_dependencies for missing node packs. This provides clear when-to-use and when-not-to-use guidance.

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