godot_duplicate_node

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the description only needs to add behavioral context beyond those flags. It does add 'deep' and the signal/script toggles, but it omits details like where the duplicate is placed, how defaults affect groups, or what scene context is required.

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 short sentence with no filler, and the core action ('deep duplicate a node') is front-loaded. It is economical and easy to scan, though the low level of detail is penalized elsewhere.

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 tool with a moderately complex schema and a large sibling set, this one-line description is minimally adequate. The output schema and annotations soften the gap, but the description does not clarify default insertion behavior, nested duplication semantics, or how the operation interacts with the scene tree and undo behavior.

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 description mentions only two optional toggles ('signal' and 'script') and provides no explanation of the required node_path, new_name, duplicate_groups, or target_parent_path behavior. With the reported schema description coverage at 0%, the description does not compensate for the six-parameter input surface, so the agent must rely entirely on the schema for parameter meaning.

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 uses a clear verb-resource pair ('duplicate a node') and adds the important qualifier 'deep', which distinguishes it from a shallow copy or simple create. It is more informative than the title 'Duplicate Node', but it does not explicitly contrast itself with sibling tools such as godot_create_node or godot_instantiate_scene.

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 phrase 'deep duplicate' plus 'signal and script flags' implies a reasonable use case: copy a node while controlling whether scripts and signal connections follow. However, there is no explicit when/when-not guidance or mention of alternatives, such as using godot_create_node for a new empty node or godot_instantiate_scene for an instanced scene.

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