set_focus

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

With no annotations, the description carries the full burden. It discloses that the tool both selects the node and scrolls the viewport, which are the key behaviors. Although it does not mention potential side effects like deselecting other nodes, the description is sufficient for a simple 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 a single sentence with no filler, perfectly concise while conveying all necessary information.

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 simplicity (1 parameter, no output schema), the description is complete. It covers what the tool does, its input, and its effect, leaving no gaps.

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% (only nodeId), so baseline is 3. The description does not add additional meaning beyond the schema's 'The ID of the node to focus on', but it is consistent and accurate.

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 the verb 'Set focus' and the resource 'a specific node in Figma', with explicit actions 'selecting it and scrolling viewport to it'. This distinguishes it from sibling tools like set_selections (which only selects) and get_selection (which reads selection).

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 implies that the tool is for focusing on a single node, suggesting it should be used over set_selections when viewport scrolling is needed. However, it does not explicitly state when to use this tool versus alternatives or mention any prerequisites.

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