n8n_start

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that n8n runs in the background and that the tool waits until the server responds at http://localhost:5678, providing useful behavioral context. However, it omits edge cases such as behavior if n8n is already running, potential side effects, or failure handling, limiting transparency.

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, direct sentence with no filler. It front-loads the action ('Inicia n8n') and efficiently conveys the background execution and wait condition, making every word earn its place.

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 start operation, the description covers the core action and the waiting behavior, which is the key contextual detail. However, there is no output schema and the return value is not described, leaving minor gaps for an otherwise simple tool.

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 input schema has zero parameters, and the baseline for no parameters is 4. The description adds no parameter-specific information, but none is required since there are no parameters to document.

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 uses the specific verb 'Inicia' (start) and clearly identifies the resource as 'n8n', distinguishing it from sibling tools like n8n_install, n8n_stop, and n8n_status. It further clarifies the action by specifying 'en background' and the target URL, making the intent unambiguous.

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 implicitly indicates this tool is for starting n8n, but it does not explicitly state when to use it versus alternatives (e.g., after installation, when status shows stopped). No exclusions or references to sibling tools are provided, so usage guidance is implied rather than explicit.

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