figma_read_variable_values

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context about behavior differences between library and consumer files, and specifies the scope (local variables only), which adds behavioral transparency beyond annotations.

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 sentences, front-loaded with clear purpose, followed by usage guidance and alternatives. No wasted words, and the structure leads with the most important 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?

Given no output schema and zero parameters, the description fully covers context: what the tool does, what it returns, when to use it in a library vs consumer file, and contrasts with a sibling tool. It is complete for the tool's complexity.

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?

Input schema has 0 parameters and schema coverage is 100%, so the description cannot add parameter semantics. Baseline score of 4 is appropriate. The description does detail the output format and use cases, which is helpful but not directly about 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?

The description clearly states the tool reads resolved values of all local variables in the current Figma file, specifies return types (names, types, hex values, numeric values), and distinguishes it from the sibling tool figma_discover_library_variables which only returns keys/names.

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 states when to use: for extracting DS token values for DESIGN.md generation, Tailwind export, drift detection. Also clarifies that it must be run in the library file for full results, and in consumer files should use figma_discover_library_variables instead, providing clear alternatives.

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