n8n_set_variables

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only specifies the bulk nature and licensing requirement. It omits critical mutation details such as whether 'set' performs upserts, creates, or updates, and whether partial failures are possible or atomic.

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 consists of two efficient sentences with minimal fluff, presenting the metadata tags and core functionality upfront. However, given the complete lack of schema documentation, this extreme brevity becomes a liability rather than a virtue, leaving too much unsaid.

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?

As a bulk mutation tool with no output schema, no annotations, and zero parameter description coverage, the description inadequately prepares the agent for invocation. It lacks return value documentation, error handling details, and parameter semantics that would be essential for correct usage.

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 has 0% description coverage for both the `site` parameter (which lacks type context or examples) and the `variables` object (which uses `additionalProperties: true` without structure guidance). The description makes no attempt to explain what constitutes a valid site identifier or the expected key-value structure for variables.

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 'Bulk set multiple variables at once,' providing specific verb, resource, and scope that distinguishes it from siblings like `n8n_create_variable` or `n8n_update_variable` which imply single-variable operations. The '[Enterprise]' tag further clarifies the target context.

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 includes a critical usage constraint stating 'Requires n8n Enterprise/Pro license,' which establishes a prerequisite for invocation. However, it fails to explicitly differentiate when to use this bulk operation versus the single-variable `n8n_create_variable` or `n8n_update_variable` alternatives.

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