list-variables

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

No annotations are provided, so the description carries full burden. It notes a critical behavioral constraint: arguments must be compact single-line JSON. It also implies a read-only operation. However, it does not disclose any other behaviors like pagination, rate limits, or side effects.

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 concise, with three short sentences. It is front-loaded with the purpose and includes important notes. No wasted words.

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 no output schema, the description does not mention return value structure. It also lacks information on prerequisites beyond enterprise license and clientId. For a list tool, missing details on filters or pagination reduce completeness.

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 100% for the single parameter 'clientId'. The description does not add extra meaning beyond the schema's description; the format note applies to the whole input. Baseline 3 is appropriate.

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 'List all variables from n8n', which is a specific verb and resource. It distinguishes from sibling tools like create-variable and delete-variable, though it doesn't explicitly contrast with other list- tools. Overall, purpose is clear.

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 mentions the Enterprise license requirement but does not provide guidance on when to use this tool vs alternatives. No when-not advice or context for choosing over other variable-related tools.

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