Copy a Qmetry test case to a different folder

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

With no annotations, the description must fully disclose behavioral traits. It states 'copy' but does not clarify whether this is a deep copy (including steps, links), whether the original remains unchanged, or any side effects (e.g., permissions inheritance). This is insufficient for safe agent invocation.

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 (12 words) that front-loads the action and resource. It is efficient, though it could benefit from minor expansion without losing conciseness.

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 4 required parameters, no output schema, and no annotations, the description is somewhat complete but lacks details on the number of test cases (array) and the non-destructive nature of copy. It adequately conveys the core operation but leaves gaps for an agent to infer.

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 input schema has 100% description coverage, so the baseline is 3. The description adds minimal value beyond the schema—it implicitly aligns 'from one folder to another' with selectedFolderId and targetFolderId, but does not explain the array nature of testcaseIds or how to obtain the IDs.

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 action ('Copy') and the resource ('a Qmetry test case') and specifies the context ('from one folder to another'). This distinguishes it from siblings like 'move-qmetry-test-case' and 'clone-qmetry-test-case', though it could explicitly note it supports multiple test cases.

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 such as 'move-qmetry-test-case' or 'clone-qmetry-test-case'. The description does not mention prerequisites (e.g., folder ID retrieval) or compare behaviors.

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