list_models

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

No annotations are provided, so the description carries the full behavioral burden. It does not state that the operation is read-only, whether it is paginated, what happens on invalid folders, or what permissions are required. For a listing tool the risk is low, but the description still omits meaningful behavioral context beyond the basic resource description.

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 efficient sentence with no wasted text. The core distinction between listing folders and listing files in a folder is front-loaded, though the telegraphic noun-phrase style slightly limits clarity.

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 tool is simple with one optional parameter, and an output schema exists so return values need not be explained. The description covers the essential resource distinction and gives folder examples, but it lacks usage guidance and explicit default behavior. It is minimally adequate for this complexity level.

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 0%, so the description must compensate for the single folder parameter. It does provide useful semantics by explaining that the folder selects files within one folder and gives concrete examples like 'checkpoints', 'loras', and 'diffusion_models'. It does not explicitly state the null/default behavior or path rules, so it only partially compensates.

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 identifies the resource clearly: model folders and files within a folder. However, it is a noun phrase without an explicit verb such as 'list', and it does not differentiate this tool from sibling listing tools like list_workflows or server_status. The purpose is inferable but not stated with verb+resource precision.

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?

There is no explicit guidance on when to use this tool versus alternatives. It implies that omitting the folder argument lists folders and providing one lists files, but this is left to inference rather than stated as usage guidance. No exclusions or prerequisites are mentioned.

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