list_local_models

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

With no annotations, description bears full burden. It discloses read-only nature, dual fallback mechanism (REST then filesystem), explains why REST is preferred (respects extra_model_paths.yaml), and notes that size/time limited to filesystem path.

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?

Description is efficient and well-structured: main action first, then fallback details, then usage guidance. Slightly verbose but each sentence adds value.

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 tool complexity (dual fallback, data differences) and no output schema, description covers all key behavioral aspects needed for correct use.

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 coverage is 100% with one parameter. Description adds value beyond schema by explaining behavior when omitted ('Lists all types if omitted') and provides examples. Baseline 3 increased to 4.

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?

Description clearly states 'List model files available to the connected ComfyUI, grouped by type' with specific verb and resource. It distinguishes from siblings by referencing search_models and download_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?

Explicitly states when to use: 'Use to see which models are already available before generating or downloading' and when not: 'use search_models to discover new models on HuggingFace, then download_model to fetch them.'

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