figma_bind_variable

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

With no annotations provided, the description carries the full burden. It discloses the plugin requirement and REST unavailability, but does not mention side effects, permissions, reversibility, or failure behavior. For a mutation tool, this is a significant transparency gap.

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?

The description is two sentences, front-loaded with the core action followed by a necessary prerequisite. No extraneous 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?

The description is brief and provides the essential action and a key constraint, but lacks details about return values, the meaning of 'property', and any side effects. Given no output schema and no annotations, the description alone may not fully prepare an agent for invoking the 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?

The description adds no parameter-level information. Schema coverage is 75% (three of four properties documented), so baseline is 3. However, the required 'property' parameter is undocumented in both schema and description, leaving a notable semantic gap.

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 action: 'Bind a variable to a node property' with a specific verb and resource. It distinguishes itself from sibling tools like figma_set_variable_value by focusing on binding rather than setting values. The plugin connection requirement further clarifies its scope.

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 explicitly states the prerequisite: 'Requires plugin connection' and excludes REST usage ('no REST endpoint for this'). This provides clear context for when the tool can be used, though it does not name alternative tools or explicit when-not scenarios beyond the REST exclusion.

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