models

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

With no annotations, the description takes full responsibility for disclosing behavior. It reveals that loading swaps the model for the entire instance, affects web UI users, takes several seconds, and switches preset/VAE/text encoder under certain architecture conditions. This is unusually transparent for such a side-effectful operation.

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 front-loaded with the key action enum. The longer paragraph earns its place by disclosing critical side effects and architectural behavior. No filler or repetition.

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 load path is thoroughly described, including side effects and architecture handling. However, the list and refresh paths are under-specified, and with no output schema and no annotations, the description does not clarify what the tool returns or how limit/query affect list results. This leaves meaningful gaps for an agent.

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 coverage is 0%, so the description must compensate. It explains action values ('list' | 'load' | 'refresh') and the purpose of preset, but it does not clarify what name, limit, or query do, which are essential for the list action. This is partial compensation for a low-coverage 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 opens with 'List or load checkpoints,' which names a specific resource and action set. It clearly identifies the tool's scope, though it does not explicitly distinguish itself from sibling tools like model_profile or loras.

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 gives explicit when-to-use guidance for the load action: 'only do it when the operator asked for that model.' It also explains when to pass a preset. However, it gives no guidance for choosing list vs. refresh or for using any sibling tool.

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