Set CivitAI Settings

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

With no annotations, the description carries full burden. It mentions server-side validation of the token but doesn't disclose whether updates are partially applied, require authentication, or if any fields are mutually exclusive. It implies a mutation (update) but lacks consequences or side effects.

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?

Single sentence, packs endpoint and key fields, front-loaded purpose. No fluff, earns its place, though it could be slightly more structured (e.g., bullet list of settings).

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 settings-update tool with 4 parameters, no output schema, and no annotations, more is needed. It doesn't explain which fields are optional, defaults, or the effect of toggles like 'save_subfolder_enabled'. The endpoint reference is helpful but incomplete.

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 only 25% (only token is described). The description lists parameter names but adds little meaning beyond the names. For example, 'save_subfolder_enabled' likely controls whether 'save_subfolder' is used, but the description doesn't explain semantics. It partly compensates by listing fields but insufficiently.

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 clearly identifies the tool as updating CivitAI integration settings, names the endpoint and lists key fields (token, save_subfolder, etc.). It is distinct from siblings like 'sdnext_civitai_search' or 'sdnext_civitai_download', which serve different purposes, though it doesn't explicitly contrast with them.

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?

No guidance on when to use this tool versus others. It doesn't mention prerequisites, when settings would need updating, or which fields are optional. The sibling context includes many CivitAI-related tools, but this description doesn't help distinguish usage scenarios.

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