Duplicate a network

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

The description discloses that the tool copies a node or entire COMP to a new node, with optional parent change, which aligns with annotations indicating a mutating (readOnlyHint=false) but non-destructive (destructiveHint=false) operation. It adds some context beyond annotations but does not elaborate on side effects or required permissions.

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, well-constructed sentence that conveys all essential information without redundancy. It front-loads the action and is appropriately concise for a simple tool.

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 straightforward duplication tool, the description is largely complete. It specifies what is copied (node or COMP), the result (new node), and optional parent. However, it does not mention whether connections or internal states are preserved, nor the return value (no output schema). These are minor omissions given the tool's simplicity.

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%, so the description does not need to add much. It mentions 'optionally into another parent' which reinforces parent_path, but adds no new meaning beyond what is already in the schema.

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 action ('Copy a node or whole COMP'), the resource ('node or whole COMP'), and includes the optional relocation aspect. The tool is distinct from sibling create_* tools, which create new empty nodes, making its purpose unambiguous.

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 create_td_node or other duplication methods. The description does not mention prerequisites, limitations, or context for use, leaving the agent to infer appropriate scenarios.

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