Copy a Qmetry test case folder

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

The description mentions 'optionally its contents', but the input schema does not include any parameter for that option, creating a contradiction. No annotations are present to clarify safety or side effects, and the description fails to reveal whether the operation is destructive or requires permissions.

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 sentence, which is concise, but it omits important details about behavior and parameters. Conciseness is acceptable, but structure could be improved by front-loading the purpose and adding critical information.

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 lack of an output schema, the description should explain what the tool returns or any side effects. The confusion about 'optionally its contents' and missing usage guidelines make the description incomplete for an agent to use correctly.

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?

All three parameters are fully described in the input schema with clear references to API responses. The description adds no new semantic value and even introduces confusion by implying a non-existent 'contents' parameter. Since schema coverage is 100%, a baseline score of 3 is appropriate.

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), the resource (Qmetry test case folder), and the optional scope ('optionally its contents'). It effectively distinguishes from sibling tools like 'move-qmetry-test-case-folder' and 'copy-qmetry-test-case'.

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-folder' or 'clone-qmetry-test-case'. The usage context is only implied by the action 'copy'.

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