editor_paste

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

No annotations are provided, so the description carries the full burden. It clearly indicates a mutation operation by saying 'Paste clipboard nodes into the scene' but does not disclose prerequisites (e.g., clipboard content, open scene) or consequences (e.g., undo support, overwriting behavior).

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 concise sentence that front-loads the verb and states the key behavior without any redundant words.

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 simplicity—one optional parameter, no output schema—the description covers the primary behavior and target location. It lacks details on preconditions like requiring clipboard contents but is sufficiently complete for a straightforward action.

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 schema already provides 100% coverage for the single 'parent' parameter with a clear description. The tool description adds no additional parameter semantics beyond echoing the default location.

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 the specific verb 'Paste' with the resource 'clipboard nodes' and states the target location ('selected node or root'), clearly distinguishing it from sibling tools like editor_copy, editor_cut, and editor_duplicate_node.

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 context for when to use the tool—pasting clipboard nodes into the scene—and explains the default parent targeting. However, it does not explicitly compare with alternatives or state exclusions, but the editor clipboard workflow is implicit.

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