Import Design Export

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

Goes well beyond the annotations by disclosing what actually happens: the file is copied into a local snapshot store, an earlier snapshot of the same frames is replaced, the source file and Figma file are untouched, and it fails if the JSON is not a valid design export. This confirms and enriches the idempotentHint and non-destructive profile.

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?

Front-loads the core purpose, then usage, behavioral effects, and failure mode in four tight sentences. Slightly long but each sentence carries distinct information; nothing is redundant filler.

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 single-parameter, no-output-schema tool with adequate annotations, the description covers purpose, sourcing, side effects, persistence semantics, and the failure condition. Nothing an agent needs to invoke it correctly 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 description coverage is 100% and the single path parameter is fully documented in the schema. The description references 'the file' and 'the JSON' but adds no format or constraint detail beyond what the schema already provides, so the baseline 3 is appropriate.

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 action (save/import a design export JSON as a snapshot) and the resource (frames with node trees as the plugin produces). It clearly distinguishes itself from the sibling save_design_export by framing this as ingesting a previously made export rather than creating one.

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?

Explicitly says to use it for an export made earlier with save_design_export or the plugin, naming the relevant sibling and the condition that selects this tool. It stops short of stating when NOT to use it (e.g. point save_design_export at it if you have not exported yet), but the context is clear.

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