cocos_duplicate_node

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

With no annotations, the description carries the full burden. It discloses key behavioral traits: the duplication is shallow (no children/components), it returns a new node index, and it's a mutation operation (implied by 'duplicate'). However, it lacks details on permissions, error handling, or side effects.

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 extremely concise (one sentence) and front-loaded with the core action. Every word earns its place, with no wasted text, making it easy to parse quickly.

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 (mutation with 3 parameters), no annotations, and an output schema (implied by 'Returns new node index'), the description is minimally adequate. It covers the basic operation and output but lacks details on parameters, error cases, and behavioral nuances.

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. It adds no parameter semantics beyond what the schema provides (scene_path, node_id, new_name). No explanation of what these parameters mean or how they affect the duplication is given.

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 specific action ('shallow-copy a node'), resource ('node'), and scope ('no children/components'), distinguishing it from sibling tools like 'cocos_create_node' or 'cocos_instantiate_prefab' which likely create new nodes or prefabs with different behaviors.

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 explicit guidance on when to use this tool versus alternatives like 'cocos_create_node' or 'cocos_instantiate_prefab' is provided. The description implies usage for duplicating nodes without children/components, but lacks context on prerequisites or exclusions.

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