figma_setup_design_tokens

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

Adds atomicity and rollback behavior beyond the destructiveHint annotation. Does not disclose side effects or permissions, but provides key behavioral 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?

Two sentences that efficiently convey purpose, behavior, and parameter list. No fluff.

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?

Lacks return value info and constraints like uniqueness of collectionName or modes. For a complex tool, extra context would be helpful, but it covers the core.

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 0%, but description lists params and briefly explains tokens structure. While it matches schema, it adds minimal new meaning (e.g., 'value? or values?'). More detail on constraints (e.g., uniqueness of modes) would improve.

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?

Clearly states it atomically creates a variable collection, modes, and variables with rollback. Distinguishes from siblings like figma_create_variable_collection and figma_batch_create_variables which handle only parts.

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?

Implies use when atomicity and rollback are desired, but no explicit when-not-to-use or alternatives compared to siblings like figma_create_variable_collection or figma_batch_create_variables.

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