set_selections

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

With no annotations, the description carries the full burden. It discloses the side effect of scrolling the viewport, which is valuable. However, it does not mention whether the existing selection is replaced, how invalid node IDs are handled, or any constraints on selecting multiple nodes.

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 concise sentence that front-loads the core action and its side effect. Every word earns its place, with no redundant information or tangential details.

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 tool with one required parameter and no output schema, this description is sufficiently complete. It states what the tool does and the notable side effect (scrolling), which is all an agent needs to know 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?

The input schema fully documents the nodeIds parameter with 100% coverage. The description's reference to 'multiple nodes' aligns with the array type but adds no additional meaning or constraints beyond what the schema provides.

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 action ('Set selection') and the resource ('multiple nodes in Figma'), plus the additional behavior of scrolling the viewport. It distinguishes itself from siblings like get_selection by focusing on the write operation.

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 should be used when one wants to set the current selection to multiple nodes. However, it does not explicitly mention alternatives or when not to use it, though the purpose is clear enough that most agents would infer the correct usage.

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