set_focus

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 transparently discloses two key behaviors: selecting the node and scrolling the viewport to it. This is meaningful beyond simply 'set focus'. It does not mention failure modes or permissions, but for a simple viewport control tool, this is adequate.

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?

A single, front-loaded sentence that states the operation and its two component actions without any fluff or repetition. Every word contributes to understanding.

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?

This is a simple, one-parameter tool with no output schema. The description fully conveys the purpose, actions, and target. For its complexity, it is complete. No missing information is critical for an agent to invoke it correctly.

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% (nodeId is described as 'The ID of the node to focus on'). The tool description repeats the same concept without adding extra syntax, format, or examples. Since the schema already documents the parameter well, baseline 3 is appropriate.

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 a specific action: 'Set focus on a specific node in Figma by selecting it and scrolling viewport to it'. This distinguishes it from sibling tools like get_selection (read-only) and set_selections (likely only changes selection without scrolling). The verb+resource+scoping is explicit.

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 context is clear: use this tool when you need to focus a node by both selecting it and scrolling the viewport. However, there is no explicit when-not-to-use or comparison to alternatives like set_selections, which might also select nodes. The implied usage is strong but lacks explicit exclusions.

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