uc_model_version_create

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

The description only states the action and endpoint, but does not disclose any behavioral details beyond the annotation 'readOnlyHint: false'. There is no mention of side effects, permissions, or constraints.

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 very short (two sentences) with no extraneous text, but it is overly sparse and lacks structure. It front-loads the action but omits essential details.

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?

Despite having an output schema, the description fails to provide a complete picture for a tool with 8 parameters. It does not mention required parameters or any workflow context. The context from annotations is minimal.

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 description adds no information about parameters. Schema coverage is only 25% (only 2 of 8 parameters have descriptions in the schema), and the description does not compensate by explaining the purpose or usage of the remaining parameters like run_id, tags, aliases.

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 'Create a model version' with the HTTP endpoint, making the action explicit. However, it does not differentiate from the sibling 'mlflow_model_versions_create' which also creates model versions but in a different system (MLflow vs Unity Catalog).

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?

No guidance is provided on when to use this tool versus alternatives like 'mlflow_model_versions_create' or conditions for creation. The description lacks any usage context or prerequisites.

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