figma_set_variant

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

Beyond annotations (idempotentHint=true, etc.), the description adds critical behavioral context: the requirement for variant axis combinations and the correct data type for BOOLEAN properties. No contradiction with 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, each carrying essential information: purpose, important caveat, and auxiliary guidance. Front-loaded with key action and mode support. No extraneous content.

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 the complexity of batch mode and variant constraints, the description covers all critical aspects. No output schema is needed for a mutation tool. The description compensates well for the absence of enums and nested object explanation in the schema.

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?

The schema already describes propertyName, value, and properties with some detail (75% coverage). The description adds value by explaining that batch mode overrides single mode and clarifying value types, but the schema's descriptions are already fairly informative.

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 it sets VARIANT or BOOLEAN component properties on an instance, supports both single property and batch modes, and distinguishes from sibling tool figma_get_component_variants which discovers available properties.

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 instructs to use figma_get_component_variants first to discover property names and values, and warns that for VARIANT properties all axes must form a valid combination, recommending batch mode. Also specifies that BOOLEAN properties require true/false, not strings.

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