Create New Flowise Flow

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

The description notes that flow_data must be a valid JSON string and indicates the return includes the new ID. Annotations show readOnlyHint=false, consistent with a write operation. No contradictions detected. Additional context about permissions or side effects would improve transparency.

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 moderately concise with a clear structure (overview, Args, Returns, Examples). The first two sentences are somewhat redundant ('Create a new...' and 'This tool creates...'), but the overall layout aids readability.

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 the tool's core purpose, input requirements (JSON flow_data), and return value (new ID). It does not address error conditions or validation details, but for a straightforward create operation with output schema present, it is sufficiently complete.

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 already contains descriptions for all parameters (name, flow_data, flow_type, etc.). The tool description restates these parameter names and adds emphasis on flow_data being JSON, but does not significantly enrich parameter 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 explicitly states 'Create a new chatflow or agentflow in Flowise,' providing a clear verb ('Create') and specific resource ('chatflow or agentflow'). This effectively distinguishes the tool from sibling operations like update, delete, or list.

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 creating new flows and provides examples for both 'CHATFLOW' and 'AGENTFLOW' types. However, it lacks explicit guidance on when not to use this tool (e.g., versus update) or alternative tools for similar tasks.

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