figma_set_rest_token

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

Discloses important behaviors: token stored only in memory, never written to disk, cleared on restart, and token expiration (max 90 days). No annotations present, so description carries full burden; it addresses security and persistence well.

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?

Three concise sentences: purpose and scope, storage behavior, and token source. No unnecessary words, front-loaded with key information.

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?

Covers purpose, usage, behavior, and token origin. For a one-parameter tool with no output schema, it is nearly complete. Could mention success response or error handling, but not essential.

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% and description enriches the parameter by specifying the token format (figd_...) and where to obtain it (Figma Settings). Adds meaning beyond the schema's brief description.

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 sets the Figma REST API token for REST API calls, listing example use cases (export, comments, version history). It distinguishes from sibling tools like figma_clear_rest_token and figma_get_rest_token_status.

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?

Provides clear context for when to use: before making REST API calls. It includes instructions on obtaining the token. However, it does not explicitly state when not to use or compare with alternatives.

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