unreal_duplicate_map

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

With no annotations, the description carries the full burden of disclosing side effects, and it does state that the operation is 'Mutating' and that it refuses while an editor is open unless allowWithEditorOpen is set. However, it does not clarify the dryRun default behavior, overwrite semantics, or what happens on refusal or success.

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?

Two sentences, no filler, with the core operation front-loaded and the critical safety condition stated immediately. Every word earns its place.

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?

This is a mutating 6-parameter tool with no annotations and no output schema, so the description needs to cover more than it does. Missing context includes the dryRun default, overwrite behavior, timeout, error handling, and return value, leaving the agent under-informed for safe invocation.

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 0%, so the description must compensate, but it only references allowWithEditorOpen and gives no explanation of sourceMap, targetMap, dryRun, overwrite, or timeoutSeconds. The property names hint at their meanings, but the description adds minimal parameter-level value.

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 a specific verb ('Duplicate'), a specific resource ('map asset'), and the '/Game/...' path scope. This clearly distinguishes the tool from siblings like unreal_list_assets, unreal_import_assets, and unreal_spawn_actors.

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 choose this tool over alternatives, nor does it mention exclusions or prerequisites beyond the editor-open condition. The editor-open refusal is a usage constraint, not a comparison with sibling tools.

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