figma_batch_update_variables

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

Annotations indicate destructiveHint=true, so the description correctly signals a write operation. It adds that up to 100 variables can be updated and that the response includes success/failure lists. No contradictions. Could mention behavior on errors.

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?

Two concise sentences with no redundancy. Immediately states capacity and item structure, then return format. Highly efficient.

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?

With one parameter (items array) and no output schema, the description covers usage and return format. Missing details like default modeId or validation rules, but adequate for a batch update tool.

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 coverage is 0%, so the description must compensate. It explains each item's structure (variableId, modeId, value) but does not define what these IDs refer to or how to obtain them. Medium helpfulness.

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 updates variables in batch, specifies the components of each item (variableId, modeId, value), and mentions return behavior (lists of updated and failed). This distinguishes it from single-update sibling figma_update_variable and batch-create sibling figma_batch_create_variables.

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 implies batch use for multiple variables but does not explicitly state when to use this tool versus figma_update_variable, nor does it provide prerequisites or exclusions. More guidance would help an agent decide.

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