create_chatflow

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only states that it creates a chatflow, omitting information about authentication requirements, whether the tool overwrites existing flows, error handling, or the structure of the response. The description adds no concrete behavioral context beyond the basic action.

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, concise sentence that immediately conveys the core action and subject. There is no filler or redundant information. It is appropriately short and front-loaded, aligning with conciseness best practices.

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 tool with four parameters, nested objects, no annotations, and no output schema, the description is notably underspecified. It doesn't explain what the user should expect in a successful response, how to structure flowData correctly, or mention related tools like list_nodes for node definitions. The description covers only the bare minimum, leaving significant gaps for a new user.

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 schema documents all parameters with descriptions, achieving 100% coverage. The description's mention of 'nodes and edges configuration' adds slight contextual reinforcement for flowData, but overall it contributes little beyond the schema. The baseline of 3 is appropriate because the schema carries the semantic load.

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 uses a specific verb ('Create') and clearly identifies the resource ('a new chatflow in Flowise') along with the key configuration aspect ('nodes and edges'). This distinguishes it from list/get/update/delete operations, though it doesn't explicitly differentiate from the create_prediction siblings. The purpose is clear and unambiguous.

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 no guidance on when to use this tool versus alternatives like update_chatflow or create_prediction. It doesn't mention prerequisites, typical scenarios, or exclusions. Users must infer its usage from the name alone.

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