list-variables

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions license requirements and input formatting, which are useful behavioral traits. However, it doesn't describe the return format (e.g., list structure, pagination), error handling, or performance characteristics, leaving gaps for a tool with no annotation support.

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 front-loaded with the core purpose, followed by critical notes in a logical order (prerequisites, usage sequence, technical details). Each sentence adds essential value without redundancy, making it highly efficient and well-structured for an AI agent.

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 tool's complexity (simple list operation), no annotations, and no output schema, the description is reasonably complete. It covers purpose, prerequisites, usage context, and input formatting. However, it lacks details on output structure and error cases, which would be beneficial for full contextual understanding.

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%, so the schema provides no parameter documentation. The description does not explain the 'clientId' parameter at all, leaving its purpose and format unspecified. However, since there is only one parameter, the baseline is 4, but the lack of any semantic information reduces it to 3, as the description fails to compensate for the schema gap.

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 verb 'List' and the resource 'all variables from n8n', making the purpose specific and unambiguous. It distinguishes itself from sibling tools like 'create-variable' and 'delete-variable' by focusing on retrieval rather than modification, and from 'get-variable' (which doesn't exist in the list) by implying a bulk operation.

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 explicit usage guidance: it states prerequisites ('Requires n8n Enterprise license with variable management features enabled'), a recommended sequence ('Use after init-n8n to see available variables'), and technical constraints ('Arguments must be provided as compact, single-line JSON without whitespace or newlines'). This covers when to use it, dependencies, and how to format inputs.

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