Move or resize

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

Annotations already indicate readOnlyHint=false and destructiveHint=true, so the description is not burdened with basic safety disclosure. It adds useful context about the auto-layout behavior, but does not elaborate on what destructive changes may occur, coordinate semantics, or the outcome when size parameters are omitted.

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?

Two compact sentences with the core function front-loaded. The second sentence earns its place by providing a critical usage caveat and routing to the sibling tool. No filler or redundant restatement.

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?

Covers the most important exclusions (auto-layout behavior) but leaves gaps for a 5-parameter tool with poor schema coverage: units, coordinate space, whether size is also ignored in auto-layout, and what 'sets' implies for existing bounds. The description is adequate for a simple case but not fully complete.

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 only 20%, with just nodeId documented. The description maps loosely to x/y/width/height by saying 'Sets position and size,' and adds one semantic constraint for x/y inside auto-layout, but it does not explain units, coordinate systems, optionality, or what happens when individual parameters are omitted.

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?

States a specific verb and resource: 'Sets position and size.' The title 'Move or resize' is clarified, and the description distinguishes itself from figma_set_layout_sizing by explicitly naming that sibling tool in the auto-layout caveat.

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?

Explicitly states when not to rely on this tool: inside auto-layout frames, position is ignored. It also names the alternative approach (figma_set_layout_sizing and parent spacing), leaving no ambiguity about the correct tool selection.

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