n8n: List variables

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

readOnlyHint=true already tells the agent this is a safe read, so the description adds little there. It contributes the license gate, but then asserts "All parameters are OPTIONAL" while the schema marks "site" as required, giving the agent a false expectation about call construction. It also says nothing about pagination behavior for limit/cursor.

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?

Very short and front-loaded, with no filler sentences, but the bracketed tags "[UNIFIED]" and "[Enterprise]" consume a large share of the text without conveying actionable meaning beyond the license sentence that follows.

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?

For a simple read-only list tool with no output schema, the minimal description is close to sufficient, and the license prerequisite is a useful addition. However, the required site parameter and the limit/cursor pagination contract are left entirely unexplained, which is a real gap given 0% schema coverage.

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 description coverage is 0% across three parameters, so the description must compensate and does not — it never explains what "site" means, what limit defaults control, or how cursor-based paging works. Worse, its only parameter statement (all optional) is contradicted by the required site field.

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 ("List all environment variables"), which is readily distinguishable from the sibling mutator n8n_set_variables and from the list_* family by resource. It is clear but does not explicitly name any alternative or scoping distinction, so it stops short of 5.

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 supplies one genuine precondition ("Requires n8n Enterprise/Pro license"), which tells the agent when the call will fail, but gives no guidance on when to prefer this over n8n_create_variable, n8n_delete_variable, or n8n_set_variables. Usage is only implied by the verb.

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