figma_create_variable_collection

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

The annotation destructiveHint:true suggests the tool may modify or delete data, but the description merely says 'Create', which is typically additive. The description does not explain the destructive behavior, such as whether creation overwrites existing collections or affects other data. This leaves ambiguity.

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 a single sentence, making it concise. However, it sacrifices essential information, resulting in an under-specified tool definition that fails to provide adequate guidance.

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 presence of sibling tools and lack of output schema, the description is incomplete. It does not explain what a variable collection is, its relationship to variables, or the outcome of creation. The agent is left without enough context to use the tool correctly.

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 input schema has 2 parameters (name, options) with 0% description coverage. The description does not explain what 'name' represents or what 'options' can contain. For a creation tool, this is insufficient; the agent cannot determine how to populate the 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 action 'Create' and the resource 'variable collection', matching the tool name. However, it does not differentiate from sibling tools like figma_create_variable or figma_batch_create_variables, leaving ambiguity about what a variable collection is.

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 provides no guidance on when to use this tool versus alternatives such as figma_create_variable or when not to use it. No context about prerequisites or suitability is given.

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