duplicate_node

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

No annotations are provided, so the description carries full burden. It discloses auto-save behavior, return value structure (originalPath, newPath), and error cases. While it doesn't mention permissions or destructive nature, cloning is inherently non-destructive and the description covers key behavioral traits.

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 efficient (6 sentences) with no redundant content. It front-loads the purpose, then provides usage context, defaults, behaviors, and errors in a logical order.

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 tool's moderate complexity and the presence of an output schema, the description covers all necessary aspects: purpose, usage scenario, parameter defaults, auto-save, return value usage, and error conditions. It is complete for an AI 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?

Input schema coverage is 100%, but the description adds value by specifying default values for newName (original name + '2') and targetParentPath (same as original), which are not implied by the schema alone.

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 'Duplicate a node and its descendants in a Godot scene' and distinguishes itself from the sibling tool 'add_node' by indicating it clones a configured subtree without node-by-node recreation.

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?

It provides explicit guidance on when to use ('clone a configured subtree without re-creating it node-by-node via add_node'), explains default behaviors for newName and targetParentPath, and mentions automatic saving and error conditions.

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