Duplicate Nodes

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

Annotations indicate non-destructive, non-read-only behavior, but the description adds no additional behavioral context. It does not mention side effects like creating new nodes in the scene or leaving originals unchanged. Parameters like 'parent_only' hint at behavior but description does not elaborate.

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?

One short sentence, no wasted words. Front-loaded with the core action.

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?

Despite having 5 parameters, a required field, and a true output schema, the description is overly terse. It does not explain the duplication process, effects of options like 'upstream_nodes', or what the tool returns. Incomplete for the complexity level.

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% with parameter descriptions, so baseline is 3. The description adds no extra parameter information, relying entirely on the schema. Agent must consult 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?

Description 'Duplicate one or more nodes' clearly states verb (duplicate) and resource (nodes). It is understandable but does not explicitly distinguish from sibling tools like 'nodes.create' which also creates nodes, though the duplication aspect is inherent. Could mention 'copies existing nodes' for better differentiation.

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 guidance on when to use this tool versus alternatives like 'nodes.create' for new nodes or 'nodes.rename' for renaming. The description lacks any context about prerequisites or scenarios where duplication is appropriate.

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