create_workflow

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

The description discloses important behaviors: offline validation is performed, invalid workflows are refused unless skipValidation=true, and workflows are created inactive. Since no annotations are provided, the description carries the full burden and does so effectively.

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 extremely concise with two sentences, the first stating the core purpose and inputs, the second adding validation behavior and follow-up action. No unnecessary information.

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?

The description covers validation, the skipValidation parameter, and the inactive state. It references the next step (activate_workflow). Given the tool's complexity and lack of output schema, this is sufficient for an agent to use it correctly.

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 coverage is 100%, so the parameter descriptions are already detailed. The description adds value by explaining the skipValidation parameter's effect and summarizing the required parameters, improving understanding beyond 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 from JSON') and specifies the key inputs (name, nodes, connections, settings). It distinguishes from sibling tools like activate_workflow by noting that created workflows are inactive.

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 guidance on when to use the skipValidation parameter and notes that activation is required afterward. However, it does not explicitly contrast with alternative creation tools like clone_workflow.

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