comfy_search_hub

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the open-world nature (public hub) and the source options, but doesn't disclose details like rate limits, pagination, or result format. With annotations covering the core safety traits, a 3 is appropriate.

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 compact and well-structured: a one-sentence purpose followed by a clear Args list. Every sentence adds value, no fluff. The examples for query are particularly helpful.

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 tool is simple (3 params, 1 required) and has an output schema, so the description doesn't need to explain return values. It covers the key usage aspects: query format, source options, and limit constraints. Slightly more detail on result ordering or error cases would push it to 5, but it's complete for the tool's complexity.

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 0%, so the description must compensate. It does: explains query with examples, source with allowed values, and limit with range (1-50) and default. This adds meaning beyond the bare schema, though it could be more detailed about result ordering or filtering.

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 searches a public model hub for models matching a query, with specific examples. It distinguishes from siblings like comfy_search_models (which likely searches local models) by specifying 'public model hub' and the source parameter (huggingface/civitai).

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 provides clear context on when to use it (searching public hubs) and implies alternatives exist (e.g., comfy_search_models for local models). It doesn't explicitly state when not to use it, but the 'public model hub' qualifier and source options give sufficient guidance.

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