set_focus

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

With no annotations, the description carries the full burden and discloses two key behaviors: it selects the node and scrolls the viewport to it. This goes beyond a simple statement of purpose, though it does not mention side effects or required permissions, which would be additional context.

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 that leads with the main action and includes necessary detail. Every word earns its place with 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?

For a simple one-parameter tool with no output schema, the description adequately covers the operation and its effect on the editor. It might have noted the need for a valid nodeId or the fact that selection changes permanently, but as a basic action description, it is sufficiently 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?

The input schema already describes the only parameter (nodeId) with 100% coverage. The description adds no extra semantics about the ID format or how to obtain it, so it only meets the baseline for schema-provided info.

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 uses a specific verb ('Set focus') and resource ('specific node in Figma'), and additionally explains the mechanism ('by selecting it and scrolling viewport to it'). This clearly distinguishes it from similar tools like set_selections, which only selects without scrolling.

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 for focusing on a node, but it does not explicitly state when to use it over alternatives, nor mention when not to use it. No exclusions or alternative tools are named, so guidance is only implied.

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