figma_set_port

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 calling this tool stops the current bridge and restarts on the new port, and that the Figma plugin must reconnect. This provides adequate transparency for a port-changing 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 three sentences with no wasted words. It is front-loaded with the main action and effect, followed by a usage scenario and a note about reconnection. Perfectly concise.

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 has only one parameter and no output schema, the description is fully complete. It covers the action, effect, usage scenario, post-requirement (reconnection), and parameter range. Nothing is missing.

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%, so baseline is 3. The description adds minimal extra meaning: it reiterates the valid range (5454–5470) which is already in the schema. It does not provide additional parameter semantics beyond what the schema offers.

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 it changes the WebSocket bridge port at runtime. It uses specific verbs ('Change', 'Stops', 'restarts') and identifies the resource ('WebSocket bridge port'), distinguishing it from sibling tools that handle other Figma operations.

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?

It explicitly mentions when to use: 'Use when the default port is busy (e.g. another AI tool holds it).' It also notes the consequence of calling (plugin must reconnect). However, it does not provide when-not-to-use or alternative tools for port-related issues.

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