set_position

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

Adds beyond annotations: explains that either coordinate can be omitted to leave unchanged, returns {ok, nodeId}, and details interaction with auto-layout. Annotations indicate readOnlyHint=false and destructiveHint=false, which are consistent.

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 sentences, front-loaded with purpose, each sentence adds essential information. No redundancy.

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 no output schema, description includes return value. Covers edge cases (omitting coordinates, auto-layout requirement). Complete for the tool's 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?

Schema coverage is 100% but description adds context: x/y are relative to parent, with specific behavior for top-level vs child nodes. Clarifies omitted coordinate means unchanged.

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?

Clearly states it sets a node's exact position (x/y) relative to its parent. Distinguishes from sibling move_nodes by specifying that move_nodes is for nudging by delta.

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?

Describes when to use: place overlay/badge/pinned element, position top-level frame. Explicitly states to avoid for in-flow auto-layout nodes unless layoutPositioning is set to ABSOLUTE first. Mentions alternative move_nodes for nudging.

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