Import or export Tokens Studio/Figma design token trees to keep design and code in sync.
Imports or exports Tokens Studio / Figma design token trees.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | Import or export action | |
| tokens | Yes | Tokens Studio JSON or Theme object |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of disclosing behavior. It only restates the import/export direction and gives no information about side effects, overwrite behavior, authentication needs, or whether the operation is a read or write.
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?
A single, front-loaded sentence with no filler. It communicates the core purpose immediately and every word earns its place.
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?
Adequate for a two-parameter tool with a fully documented schema, but with no annotations and no output schema, it omits behavioral and return-value details an agent might need to fully understand the consequences of a sync operation.
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 description coverage is 100%, and the schema already documents the 'action' enum and 'tokens' object. The description adds no additional parameter-level meaning, but the schema fully covers the parameters.
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?
States a specific verb ('Imports or exports') and resource ('Tokens Studio / Figma design token trees'), making the tool's role unambiguous and distinct from the sibling generate, mutate, and export tools.
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 gives clear context for when to use the tool: synchronizing Tokens Studio/Figma design token trees. However, it does not explicitly name sibling alternatives or state when not to use them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.