Move, resize or reparent nodes

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 states 'Set absolute position, size, or parent container' which implies mutation, but it does not disclose potential side effects like overwriting existing values, behavior on reparenting child nodes, or failure conditions.

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 two sentences with no fluff. First sentence states the function, second gives practical scenarios. It's front-loaded and easy to scan.

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 complexity (array of up to 300 items with multiple properties), no annotations, and no output schema, this description is not complete. It covers high-level purpose but lacks behavioral details and parameter semantics needed for safe invocation.

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 must compensate. It mentions 'absolute position, size, or parent container' but does not clarify coordinate units, default behavior, or the meaning of parentId values beyond what the schema already says (which itself only explains nodeId and parentId).

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 that the tool sets absolute position, size, or parent container for existing nodes, naming specific capabilities and resource. It distinguishes from sibling tools like create_shapes, delete_nodes, and even update_nodes by focusing on layout operations.

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 explicit use cases: tidying a board after content generation and moving nodes into a section. It doesn't explicitly mention alternatives or when not to use it, but the context is clear enough for an agent.

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