Add Test Case version

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

No annotations are provided, so the description must convey behavioral traits. It merely states 'create a new version' but omits critical details: that it copies from an existing version, whether the original is modified, any permission requirements, or side effects. This is insufficient for a mutation tool.

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 efficiently conveys the core purpose. Every word is necessary and no redundancy exists. It is appropriately concise for a simple operation.

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 the absence of an output schema and the fact that it is a mutation tool, the description is too minimal. It omits important context such as the effect on existing versions, the required source version, and the nature of the versioning. The schema provides parameter details, but the description should supplement with behavioral context.

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 100%, with clear descriptions for all parameters. The tool description adds no further meaning beyond the schema, so the baseline of 3 is appropriate. No additional context is provided for parameters.

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 the tool's function: 'Create a new version of an existing test case'. This distinguishes it from siblings like 'create-qmetry-test-case' (new test case) and 'clone-qmetry-test-case' (clone of entire test case), as it specifically creates a version.

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 clone or update. It does not mention prerequisites, typical scenarios, or when not to use it. The 'copyFromVersion' parameter hints at the behavior, but the description lacks explicit usage context.

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