comfy_search_models

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

The description adds behavioral details beyond the annotations: it clarifies that the query is case-insensitive, the default folder scope, and the effect of `include_non_model_files`. These details complement the readOnly and idempotent hints without contradicting them.

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 concise—three sentences—and directly addresses the tool's behavior and parameters. No unnecessary wording or redundancy.

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?

The description gives enough context for a user to understand what the tool does, its default and optional behaviors, and the meaning of each parameter. It does not describe the return format, but that is not critical for a search tool and may be covered by an output schema not shown here.

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?

Each parameter is thoroughly explained: `query` is a case-insensitive substring match, `folders` restricts the search, and `include_non_model_files` includes specific file types. This fully covers the schema's properties with meaningful 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 the tool's purpose: 'Search for models by name across folders.' It specifies the resource (models) and the action (search), distinguishing it from sibling search tools for nodes, techniques, and history.

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 explains default behavior (searches all folders) and provides an explicit example of narrowing with `folders`. It also clarifies the `include_non_model_files` parameter. However, it does not explicitly mention when not to use this tool versus other search tools, though the context is fairly clear.

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