figma_preload_styles

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

Adds context beyond annotations: batch import, instant resolution, timeout penalty. Annotations provide idempotent and non-destructive hints, no contradiction.

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, usage timing, benefit. No filler, logically ordered.

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 caching tool with one parameter and no output schema, the description fully covers when and why to use it, and what the parameter is for.

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 covers the 'keys' parameter fully. Description adds build context (all keys needed for build) to the parameter meaning.

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?

Description clearly states it batch imports DS text and color styles into cache. Differentiates from siblings like figma_discover_library_styles and figma_create_text by specifying it's a preload step.

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 call at build start with all needed keys. Explains benefit (avoids 8-second timeout) but does not explicitly state when not to use.

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