CivitAI Legacy Search

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

The description discloses it is a legacy endpoint and indicates a GET request, implying read-only behavior. However, it lacks explicit statements about side effects or permissions, though for a search these are likely minimal.

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 two concise sentences, directly stating purpose and alternative, with no unnecessary fluff.

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 is minimal, lacking explanation of parameters, output, or the exact differences from the v2 endpoint. It does not sufficiently cover the tool's functionality given its 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?

The description provides no additional meaning for any of the 10 parameters. The schema itself has no descriptions, so the description fails to compensate for the low schema coverage.

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 it is a legacy CivitAI search endpoint and differentiates it from the v2 alternative, making its 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?

It explicitly instructs to use sdnext_civitai_search for the v2 API, clearly indicating when to avoid this tool and pointing to the preferred alternative.

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