create_workflow

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

Annotations cover read-only and destructive hints without contradiction. The description adds that the tool returns 'workflow_id + node summary' and that a template can seed the workflow, which is helpful. Still, it doesn't clarify persistence, side effects, or what happens if the template is invalid.

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?

Two tight sentences, front-loaded with the core action, and no redundant wording. Every phrase adds signal: blank vs template, recommendation, template source, and output.

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 creation tool with a single required parameter and one template optional parameter, the description is mostly complete. The return value is mentioned, and the template source is provided. Minor missing detail is what exactly a node summary contains, but the presence of an output schema lowers the burden on the description.

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 schema description coverage at 0%, the description partially compensates by explaining that 'template' seeds from a bundled template and telling the user to consult list_templates. However, it does not explain the required 'title' parameter or specify the expected template identifier format.

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 identifies the operation: start/create a workflow, with the key options 'blank' or 'seeded from a bundled template'. It also signals the output. However, it does not explicitly distinguish itself from sibling tools like run_workflow, import_workflow, or save_workflow.

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?

It gives useful context about when to prefer a template ('recommended for current model families') and points to list_templates. However, it does not clearly state when to use this tool over alternatives such as import_workflow or run_workflow, or provide any when-not-to-use guidance.

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