Resolve Model Path

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

With no annotations provided, the description carries the full burden. It only says 'Resolve the local save path' and includes a GET endpoint, which implies a read-only operation, but it does not disclose authentication needs, error behavior, or what happens when no match is found. This is minimal transparency.

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 a single, front-loaded sentence with no fluff. The parenthetical endpoint is useful. However, it is so terse that it sacrifices necessary detail, but for what it includes, it is concise and well-structured.

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?

Despite having 8 optional parameters, no output schema, and no annotations, the description only states the core action. It lacks information about return values, how parameters combine, required inputs, and behavioral side effects, making it inadequate for an agent to use the tool correctly.

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 schema has 8 parameters with 0% description coverage, and the description does not mention any parameter or explain how to specify a model/version. It simply says 'model/version' without indicating how the 8 optional fields (model_id, version_id, model_name, etc.) are used, providing no added meaning 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?

The description clearly states the tool's function: 'Resolve the local save path for a CivitAI model/version' with the specific endpoint. This distinguishes it from sibling tools like download, search, or model info. It also includes the HTTP method, adding specificity.

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 no guidance on when to use this tool versus alternatives such as sdnext_civitai_download or sdnext_civitai_check_local. It does not mention any prerequisites, conditions, or which parameters are typically needed, leaving the agent without context for selection.

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