n8n_delete_variable

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

No annotations are provided, so the description carries the full burden. While 'Delete' implies destruction, the description fails to disclose whether the deletion is permanent, if it affects running workflows referencing the variable, or any cascading effects. It only states the action type without behavioral details.

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 compact and front-loaded with the action. The '[UNIFIED] [Enterprise]' metadata prefixes are slightly noisy but do not significantly detract from the core message. No redundant or wasted sentences.

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 deletion operation, the description covers the licensing context adequately. However, given the 0% parameter schema coverage and lack of output schema, the failure to document the 'site' and 'key' parameters represents a significant gap that prevents complete 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?

With 0% schema description coverage for both 'site' and 'key' parameters, the description completely fails to compensate. It does not explain that 'site' refers to the n8n instance identifier or that 'key' is the variable name, leaving the agent without guidance on parameter values.

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 explicitly states 'Delete an environment variable' with a clear verb and resource. It effectively distinguishes from siblings like n8n_create_variable, n8n_update_variable, and n8n_list_variables through the specific action verb.

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 the critical prerequisite 'Requires n8n Enterprise/Pro license,' which establishes when the tool can be used. However, it does not explicitly mention alternatives (e.g., using n8n_update_variable for modifications rather than deletion).

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