search_civitai_models

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

Discloses read-only and network-only nature, API token unlocking gated results, and SFW-only default. Describes return fields (model_id, version_id, trigger words) despite no output schema. Lacks mention of pagination or rate limits, but overall transparent for a search tool.

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 somewhat verbose but well-structured: starts with purpose, then usage guidelines, parameter details, and flow. Each sentence contributes meaning, though could be tightened slightly.

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 absence of output schema, description explains return values (model_id, version_id, trigger words) and the complete search-to-wire flow. Covers all 7 parameters with actionable advice, and mentions necessary API token. Very thorough.

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?

Even with 100% schema coverage, description adds significant value: example values for query, exact labels for base_models, enumeration of model types, clarification that creator requires exact username and can be found via sibling tool, and defaults for sort and limit. This enriches understanding beyond the schema.

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 begins with 'Search CivitAI by keyword for checkpoints, LoRAs, embeddings, VAEs, and ControlNets', clearly stating the verb, resource, and scope. It explicitly distinguishes from sibling 'search_models' for HuggingFace, making the purpose unambiguous.

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?

Provides explicit when-to-use ('THE tool for find me a <base model> LoRA on Civitai'), when-not-to-use ('For HuggingFace search use search_models'), and usage tips (always pass base_models when checkpoint known, use search_civitai_creators for exact username). Gives a complete flow: search -> download -> wire.

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