Add nodes to scene

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

With no annotations, the description carries the transparency burden. It discloses that the scene file is rewritten, which is a useful side-effect warning. However, it does not mention the potential loss of script references when force is true, nor does it state that changes are permanent. This is a notable gap for a write operation.

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 only two sentences, with the primary purpose front-loaded. Every clause adds value: batching guidance and the rewrite side-effect. No fluff.

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?

The tool is relatively simple, and the schema covers parameter semantics thoroughly. The description covers the key behavioral aspects (single save, rewrite). However, it does not mention what the tool returns (no output schema), nor does it call out the force/script-reference risk in the main description, though the schema does. This is adequate for the complexity.

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 provides 100% coverage for all four parameters, with detailed descriptions for each (e.g., force, nodes order, parent default). The description adds little beyond batching guidance, so the baseline of 3 is appropriate.

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 tool adds one or more nodes to a scene in a single save. The verb 'Add' and resource 'nodes to a scene' are specific, and the 'single save' detail distinguishes it from modifying or inspecting nodes.

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 advises batching related nodes and warns that each call reloads and rewrites the scene file, implying that batching reduces overhead. However, it does not explicitly mention alternatives like node_modify for modifying nodes or scene_create for creating scenes, so it stops short of a 5.

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