u1_list_models

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

With no annotations, the description carries the behavioral transparency burden. It does add useful scope information: only STL/3MF files inside U1_MODEL_DIR are listed. It does not disclose ordering, recursion behavior, error conditions, or explicitly state that it is read-only, though 'List' implies a non-mutating 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 a single front-loaded sentence that states the action, resource type, and location with no filler. Every word contributes meaning.

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 zero-parameter listing tool with an output schema present, the description is nearly complete. It identifies what is listed and where, and the output schema presumably covers return structure. The only missing contextual element is explicit guidance on how this tool fits into a workflow with the many sibling tools.

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, so the schema coverage is effectively complete. The description does not need to explain parameters, and it correctly adds only resource and location context. Baseline for a zero-parameter tool is 4.

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 is a specific verb+resource statement: 'List STL/3MF models inside U1_MODEL_DIR.' It names the file types and the directory scope, which clearly distinguishes this from sibling tools like u1_inspect_model, u1_transform_model, or u1_list_profiles.

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 usage: call it when you need to enumerate available STL/3MF models. However, it does not explicitly state when not to use it or point to alternatives such as u1_inspect_model for model details, leaving the agent to infer routing from tool names.

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