Create Workflow

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

Annotations indicate readOnlyHint=false, so the write nature is already known. The description adds no further behavioral information—nothing about duplicate handling, required flow_data, authentication, or side effects. It does not contradict annotations, but fails to enrich them.

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 a single sentence that essentially restates the tool name ('Create a new workflow' vs 'Create Workflow'). While short, it is under-specified rather than informative, and the sentence does not earn its place by adding unique value.

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?

With no output schema and a one-sentence description, the tool lacks contextual completeness. It does not explain what a workflow is, what flow_data should contain, or any operational context. For a create operation with multiple parameters, more context is needed for reliable invocation.

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 provides 100% parameter descriptions (flow_name, flow_data, api_key), so the baseline is 3. The description itself contributes no parameter semantics; it does not mention any of the parameters or their roles. Since schema coverage is complete, no penalty is applied.

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 'Create a new workflow' clearly identifies the action (create) and resource (workflow), distinguishing it from siblings like lyzr_update_workflow, lyzr_get_workflow, and lyzr_delete_workflow. It is a straightforward purpose statement, though it adds little beyond the title.

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 gives no guidance on when to use this tool versus alternatives. It does not mention prerequisites, how it relates to update/get/delete workflow tools, or any context for when creation is appropriate. There is no usage direction beyond the stated purpose.

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