n8n_create_workflow

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It only says 'create a new workflow' and gives no details about side effects, return values, default states (e.g., active=false), authentication needs, or validation behavior. This is a complete lack of behavioral 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 only one short sentence, but it provides almost no useful content beyond the tool name. This is under-specification rather than conciseness. It does not even mention the required parameters (name and nodes) or any operational context.

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 creation tool with 5 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what happens on success, what the response looks like, or any constraints on the workflow structure. The schema covers the fields but the tool's behavior and practical use remain unexplained.

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 100% coverage with descriptions for all 5 parameters, including default values (e.g., active defaults to false). The description adds no additional parameter information, but the schema already does a sufficient job. This matches the baseline of 3 for high schema coverage.

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 'Crear un workflow nuevo en n8n' is essentially a restatement of the tool name 'n8n_create_workflow'. It does not add any specific detail about what creating a workflow involves or how it differs from sibling tools like update or delete. This qualifies as a tautology.

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 no guidance on when to use this tool versus alternatives such as n8n_update_workflow or n8n_delete_workflow. There is no mention of prerequisites, typical scenarios, or when not to use it. The only implied usage is the obvious fact that it creates a workflow.

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