create-model-version

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

No annotations provided; description does not disclose behavioral traits such as whether it auto-increments version numbers, errors on duplicate, or requires a registered model. Completely opaque.

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?

Extremely terse (5 words) but under-specified. It essentially repeats the tool name and adds no value. Not earning its place.

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 6 parameters, no output schema, no annotations, the description is woefully incomplete. Missing prerequisites, return values, side effects, and relationship to other model operations.

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 50% (borderline low/high). The description adds no parameter information, but baseline is 3 as per rules. It does not compensate for the missing schema descriptions of runId, runLink, etc.

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 'Create a new model version' clearly states the action but does not differentiate from siblings like create-registered-model or create-logged-model. Context needed: model version is part of registered model lifecycle, which is not mentioned.

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 usage guidance provided. Description does not indicate when to use this tool versus alternatives like create-registered-model, nor does it mention prerequisites such as existence of a registered model.

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