uc_model_list

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

The readOnlyHint annotation already indicates a safe read operation. The description adds no behavioral traits beyond stating it lists models. It does not disclose pagination, filtering, or any other behavioral aspects that the schema parameters hint at.

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 extremely concise, consisting of a single sentence plus the endpoint. While front-loaded with purpose, it lacks essential information about parameters and usage, making it too sparse to be fully useful.

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?

Given that the tool has an output schema, the description does not need to explain return values. However, it omits important context such as filtering, pagination, and how this tool relates to other model-listing tools. The description is incomplete for a list operation with four parameters.

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%, yet the description does not explain any of the four parameters. The agent must rely solely on property names ('Catalog Name', 'Schema Name', etc.), which offer incomplete guidance. No additional semantic information is provided.

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 "List registered models", which is a specific verb+resource. The underlying REST endpoint is also provided for reference. While it does not explicitly differentiate from sibling list tools, the name and description together make the purpose clear.

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 like mlflow_registered_models_list, nor does it explain the typical usage context, such as filtering by catalog or schema. There is no mention of pagination or the optional parameters.

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