check_model_exists

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

With no annotations, the description carries the full burden; it does disclose that the check is performed against object_info model lists (useful behavioral detail) and that COMFYUI_HOST must be configured. It does not state the return shape (presumably boolean), failure behavior, or whether the server is queried live each call.

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?

Two short sentences, zero waste, with the core purpose front-loaded and the environment prerequisite trailing usefully.

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 simple two-parameter existence check with fully documented schema, this is nearly complete; the only gap is the unstated return value, which is not covered by an output schema.

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%, with both 'name' and an enumerated 'type' documented in the schema, so the baseline is 3. The description adds no extra semantics about filename format or type matching.

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?

States a specific verb ('Check') and resource ('if a model exists on the ComfyUI server'), and clarifies the backing data source ('object_info model lists'), which distinguishes it from list_models/get_model_info. It does not explicitly name those siblings as alternatives, so it falls short of a 5.

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?

'Requires COMFYUI_HOST' gives a prerequisite, and the name plus description imply a pre-flight existence check, but there is no explicit when-to-use vs. list_models, get_model_info, or check_compatibility guidance.

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