n8n: Create workflow

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description contributes a genuine behavioral fact beyond that: the workflow is created inactive by default. It says nothing about name-uniqueness, required permissions, or what happens on failure, which matters for a non-idempotent mutation.

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?

Three short sentences, front-loaded with the action and followed by the two facts most likely to cause a bad call. No filler; the '[UNIFIED]' prefix is the only low-value token.

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 six-parameter, zero-coverage mutation tool with no output schema, the description leaves too much to the schema, especially the required 'site' argument. It does cover the inactive-by-default behavior and the optionality of settings/static_data, which are the main traps.

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?

Schema description coverage is 0% across six parameters, so the description has to compensate and largely does not. It clarifies only that settings and static_data are optional and that the body is a 'JSON definition,' leaving the required 'site' parameter, plus 'nodes' and 'connections', entirely unexplained.

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?

States a specific verb and resource: 'Create a new workflow from JSON definition,' which clearly separates it from the activate/deactivate/delete/get siblings. It does not address the more ambiguous neighbors (n8n_import_workflow, n8n_duplicate_workflow), which an agent could plausibly confuse with it.

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?

There is no explicit when-to-use guidance and no comparison to alternatives such as import or duplicate, which overlap meaningfully with creating from JSON. The only guidance is a note to omit optional fields, which is field-level advice rather than tool-selection advice.

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