n8n_get_variable

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action of getting a variable, without mentioning what is returned, error handling, permissions, or side effects. For a getter, the return format and behavior on missing IDs are critical but not explained.

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, concise sentence that is front-loaded with the verb and resource. There is no unnecessary information, and it is easy to parse.

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?

The tool has one parameter, no annotations, and no output schema. The description explains the basic action but omits the return value, error conditions, and any other behavioral context. For a get operation, this leaves the agent without sufficient information to handle the response properly.

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 fully documents the single parameter 'variable_id' with a description, achieving 100% schema coverage. The description adds only 'by its ID', which is redundant with the parameter name. The schema carries the semantic weight, so a baseline of 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 the action: retrieve a specific variable by its ID. It uses a specific verb 'Obtener' and identifies the resource 'variable'. It distinguishes from n8n_list_variables by emphasizing 'una variable específica' and 'por su ID', though it does not explicitly name alternatives.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention that listing all variables requires n8n_list_variables, nor does it explain prerequisites such as needing a valid variable_id. No exclusionary or alternative context is provided.

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