set_node_position

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

The description adds the meaningful qualifier 'in the editor,' indicating this is an interface-layout change rather than a world/object transform. The idempotentHint annotation is consistent and covers repeat-call safety, but the description does not disclose the coordinate format, whether the change affects rendering, or any prerequisites such as the node existing.

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 single sentence is concise, front-loaded, and contains no filler. It is not overlong, though the brevity contributes to missing parameter-level detail.

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 tool with three required, opaque parameters and no schema descriptions, the description is too thin. It does not explain how to identify the material/node, what location values mean, what coordinate space the editor uses, or how this relates to the many sibling node tools.

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 carries the full burden for explaining material, node, and location. It only parses as 'node' + 'position' and says nothing about the material parameter, node identifier format, or the expected shape/order of the location array.

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 a specific verb and resource: 'Set a node's position in the editor,' which clearly distinguishes the operation from object transforms or node value edits. However, it does not state which node context (material, geometry, compositor) applies, and the required 'material' parameter is not reflected in the wording.

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?

The phrase 'set a node's position in the editor' implicitly tells the agent this is for manual node layout in a node editor, differentiating it from transform tools. It provides no explicit when-to-use versus alternatives, no exclusions, and no note about alternatives such as layout_node_tree.

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