List UNet/DiT

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

With no annotations provided, the description carries the full burden. It discloses that the tool performs a read-only listing and maps to a GET endpoint, implying safety, but it does not describe return format, pagination, or any other behavioral caveats. For a zero-parameter list tool this is adequate but thin.

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, tightly constructed sentence that front-loads the action and resource and appends the endpoint in parentheses. Every token earns its place with zero 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?

For a simple zero-parameter listing tool, the description conveys what is listed and the endpoint, which is mostly complete. It does not explain what fields the returned model list contains, but given no output schema and a trivial operation, this is a minor gap.

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 input schema has zero parameters and schema coverage is trivially 100%, so the baseline for 0 params is 4. The description adds no parameter information, but none is needed since the tool takes no inputs.

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 verb 'List' and the resource 'UNet/DiT models', and the parenthetical endpoint (GET /sdapi/v1/unets) further differentiates it from sibling tools like sdnext_list_checkpoints and sdnext_list_vae. This is a specific and unambiguous purpose statement.

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 implies its use case via the resource name but provides no explicit guidance on when to use this tool versus alternative list tools, and it names no exclusions or alternatives. The context is clear but no directional guidance is given.

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