create-workflow

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

With no annotations provided, the description carries full burden. It discloses important behavioral traits: JSON formatting requirements, mandatory structure elements (nodes/connections arrays), and read-only property exclusion. However, it doesn't cover permissions, error conditions, or response format, leaving gaps for a mutation tool.

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 appropriately sized and front-loaded with the core purpose. The two IMPORTANT points are necessary for correct usage, though the second point could be more concise. No wasted sentences, but minor structural improvements possible.

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 4-parameter mutation tool with no annotations and no output schema, the description provides adequate technical constraints but lacks completeness. It covers JSON formatting and structure requirements well, but doesn't explain what happens after creation, error handling, or relationship to other tools like 'activate-workflow'.

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 4 parameters, the description compensates well by explaining that 'nodes' and 'connections' must be provided as arrays/objects (even if empty), and that 'active' property should be excluded. It doesn't detail 'clientId' or 'name' semantics, but provides crucial structural guidance missing from the schema.

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 action ('Create a new workflow') and resource ('in n8n'), with additional context about optional nodes and connections. It distinguishes from siblings like 'update-workflow' or 'get-workflow' by focusing on creation, though it doesn't explicitly compare to all siblings.

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 for setting up new workflows, but doesn't explicitly state when to use this versus alternatives like 'init-n8n' or 'update-workflow'. It provides technical requirements (JSON format, structure) but lacks contextual guidance on prerequisites or typical scenarios.

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