figma_import_library_variable

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

With no annotations present, the description carries the full burden and does so: it discloses idempotency ('calling it twice returns the same local id'), the failure mode (importVariableByKeyAsync rejects when the library is not subscribed), the plugin prerequisite, and post-import behavior (variable becomes locally addressable).

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?

Front-loaded one-line purpose, then workflow, then prerequisites in bold-labeled blocks. Every sentence conveys actionable information — idempotency and the reject condition are not filler.

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?

No output schema exists, yet the description explains what is returned (a local 'id') and how to use it downstream with binding tools. Prerequisites, idempotency, and follow-on tools are all covered, leaving nothing an agent needs missing.

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 100% and the schema already explains that variableKey comes from figma_get_library_variables and is distinct from the local id. The description reinforces the workflow but adds no syntax or format detail beyond the schema, so this is the baseline 3.

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?

States a specific verb and resource: importing a single variable from a subscribed team library into the current file. It is clearly distinguished from figma_get_library_variables, which is named as the step that produces the key this tool consumes.

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?

Provides an explicit three-step workflow with the prerequisite lookup tool named, plus a REQUIRES clause stating the Desktop Bridge plugin and library subscription condition. The agent knows exactly when this tool applies and what must hold before calling it.

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