test_duplicate

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds a useful detail: the default generated name when newName is omitted. However, it does not mention collision behavior, permissions, or whether the original remains untouched, which is important for a mutation-like operation with no annotation coverage.

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, polished sentence that front-loads the core operation and includes the essential default behavior in a parenthetical. There is no filler or redundancy.

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 simple two-parameter duplication tool, the description plus schema is mostly sufficient for selecting and invoking it correctly. However, with no annotations and no output schema, it leaves return behavior and error/name-collision semantics unspecified. It is adequate but not fully complete.

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 coverage is 100%, so both parameters are already documented. The description adds meaningful value by clarifying that newName is optional and defaults to '<name> (copy)', which is not expressed in the schema. This goes beyond the schema's terse 'New name'.

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 explicitly states 'Duplicates an existing test under a new name', naming both the operation and the resource with a specific verb. The default naming parenthetical adds further precision. This clearly distinguishes the tool from sibling operations like test_create and test_rename.

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 verb 'Duplicates' implies the intended use case, and 'existing test' signals that it applies to already-saved tests. However, it does not explicitly mention alternatives such as test_create or test_rename, nor does it state when not to use this tool. Usage guidance is implied rather than explicit.

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