set_node_position

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

With no annotations, the description carries full disclosure responsibility. It only states the core action and auto-detect behavior, but does not reveal side effects like whether the scene is saved, whether the scene must be open, or error behavior. This is a significant gap for a mutation tool.

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 one sentence, front-loaded with the action, and has zero waste. It efficiently conveys the primary purpose and a helpful behavioral note in minimal space.

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 simple setter with no annotations, the description is too thin to cover essential context such as whether it operates on the open scene, if changes are saved, or any permissions required. The schema covers parameters, but the overall tool context remains incomplete.

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 100%, so the baseline is 3. The description adds no additional parameter detail beyond the schema. The auto-detect hint relates to the value parameter but does not enrich the schema's own format explanations.

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 'Set node position' uses a specific verb and resource, clearly identifying the tool's action. It distinguishes from siblings like set_node_rotation and set_node_scale by naming the exact property. The added '2D/3D auto-detect' further clarifies the scope.

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 description provides no guidance on when to use this tool versus alternatives such as transform_node or set_node_rotation. It does not mention exclusions or prerequisites. The only hint is 'auto-detect' regarding input formats, which is not usage direction.

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