Delete Flowise Flow

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

Adds information about irreversibility and return confirmation beyond annotations, but annotations already indicate destructive and idempotent traits; no new behavioral traits disclosed.

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?

Clear and well-structured with purpose, warning, and return; slight redundancy with schema but no unnecessary content.

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?

Covers basic action and warning but lacks details on error cases, prerequisites (e.g., flow must exist), or effects on dependent resources.

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 already provides description for flow_id; description only repeats parameter purpose without adding new meaning.

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 the verb 'Delete' and resource 'chatflow or agentflow', clearly distinguishing from sibling tools like create or update.

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?

Includes a warning about irreversibility, which is a strong usage hint, but lacks explicit when-to-use or alternatives compared to other sibling tools.

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