delete_flow

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

The description is clear about the irreversible, destructive nature of the operation: 'Permanently remove', 'destructive and irreversible', and 'cannot be recovered unless previously backed up'. It also covers common errors like unauthorized access and active flows, which adds 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 well-structured with clear sections including Purpose, Parameters, Returns, Usage Examples, Best Practices, Common Errors, and Related Tools. While lengthy, it is organized and front-loaded with the purpose. Each section adds value, though some repetition could be trimmed.

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?

Given the simple input schema (one parameter) and no output schema, the description is comprehensive. It includes return object specification, common errors, usage examples, and best practices. It covers all necessary context for an agent to safely and correctly invoke the tool.

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 single parameter 'flow_id' is described in the description with its type (UUID string) and guidance on how to obtain it (from list_flows or get_flow). The schema already provides basic description, but the tool description adds context and best practices, exceeding the baseline.

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 states the tool's purpose: 'Permanently remove a single flow from Langflow instance.' It uses specific verbs like 'remove' and identifies the resource 'flow'. It distinguishes from sibling tools like 'delete_flows' for batch operations.

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 explicitly states when to use the tool (e.g., cleaning up test/development flows) and provides best practices including when not to use it (e.g., if flow is in production). It also mentions alternatives like 'delete_flows' for bulk operations and 'download_flows' for backup.

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