list_models

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

With no annotations, the description carries the burden. 'List' clearly indicates a read-only operation with no side effects, which is adequately transparent for a simple listing function. It does not disclose output format or edge-case behavior, but these are not critical for a straightforward list operation.

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 that precisely conveys the tool's purpose without unnecessary detail or repetition. Every word earns its place.

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 list operation with a single parameter fully documented in the schema, the description provides sufficient context. It specifies the environment (spark) and the resource type (ComfyUI models subdir), making it complete for an agent to 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?

The schema provides 100% coverage for the single required parameter 'kind' with a description and enum values. The tool description adds no additional meaning about the parameter, so the baseline score of 3 is appropriate given the schema already fully documents it.

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 the action: list installed model files in a specific subdirectory. The verb 'list' and resource 'model files' are unambiguous, and the scope 'ComfyUI models subdir on spark' distinguishes it from sibling tools like list_outputs and list_workflows.

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 implies when to use the tool (when needing to list model files) but provides no explicit guidance on alternatives or exclusions. There is no mention of sibling tools or when not to use this tool, leaving the agent to infer from the name and context.

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