Create product version

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

Annotations only include destructiveHint:false, so the description carries the burden. It discloses a key default (product defaults to KIWI_PROJECT) but does not mention side effects, required permissions, or return behavior. This adds some behavioral context but leaves significant gaps.

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 concise sentence, easy to scan. However, 'Version.create' is a bit cryptic and could be clearer, but it is still efficient.

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 creation tool with no output schema, the description should explain what is returned or what success looks like. It only describes the input behavior and default, leaving the outcome unspecified. This is a notable gap for agents deciding whether to invoke the tool.

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 schema already documents both parameters, but the description adds the default value for product (KIWI_PROJECT), which is not in the schema. This enhances understanding of the product parameter and its optionality.

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 states 'Version.create' and 'value plus product', making it clear this tool creates a version. It is distinct from sibling kiwi_list_versions. However, the wording is terse and relies on the title for full clarity, so not a 5.

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. There is no mention of scenarios or exclusions, and the sibling list contains no related create tool except this one, but that doesn't substitute for explicit usage instructions.

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