n8n_install

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

No annotations are provided, so the description must disclose behavior. It states the exact command and that the installation is global, implying a system-wide change, but it does not mention potential side effects like requiring sudo, network access, or whether it can be safely rerun.

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, focused sentence that front-loads the core action (installs n8n) and the method (npm install -g n8n). No unnecessary words or filler—excellent conciseness.

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, zero-parameter install tool, the description covers the essential action and provides the underlying command. It could mention prerequisites like network access or sudo, but given the tool's simplicity and the empty schema, the description is reasonably complete.

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 zero parameters, the schema is empty and the baseline for this dimension is 4. The description provides the actual command executed, which adds semantic context beyond the empty schema by detailing the installation method.

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 tool's function: installing n8n globally on the machine using a specific npm command. The verb 'Instala' is specific and the resource is unambiguous, distinguishing it from sibling tools like n8n_start or n8n_stop.

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 implies usage context: it is for installation, not for starting/stopping or managing workflows. However, it does not explicitly mention alternatives or when not to use this tool, relying on the user's understanding of sibling tool names.

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