set_focus

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

The description discloses that the tool both selects the node and scrolls the viewport, which are key behavioral side effects. With no annotations, this is useful context, though it doesn't mention error cases or permissions.

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, efficient sentence that immediately conveys the purpose and mechanism with no superfluous words.

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?

For a simple one-parameter tool, the description adequately explains the action and its effect. While there is no output schema or mention of return values, the behavior is simple enough that the agent can infer the outcome without further detail.

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?

The schema fully documents nodeId as 'The ID of the node to focus on' (100% coverage), and the description does not add additional parameter-specific details beyond the schema. Baseline 3 applies.

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 tool's action ('Set focus on a specific node in Figma') and its mechanism ('selecting it and scrolling viewport to it'), distinguishing it from sibling tools like get_selection or set_selections.

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 the tool is used when you need to focus on a specific node, but it does not explicitly contrast it with alternatives like set_selections or get_selection. No exclusions or conditions are stated.

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