Delete a workflow flow by name. Confirmation is required to remove the default start-task flow.
Eliminar un flow. El flow "start-task" requiere confirm: true.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Nombre del flow a eliminar | |
| confirm | No | true para confirmar eliminacion del flow default |
Changes observed during successful MCP inspections.
v0.1.15Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It labels the operation as deletion but does not mention permanence, side effects, required permissions, or consequences. The only additional behavioral detail is the narrow confirm requirement for the 'start-task' flow, leaving much undisclosed.
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?
Two short sentences: the first states the action directly, the second adds a relevant edge case. No filler or redundant restatement of the schema.
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 destructive tool with no annotations and no output schema, the description covers the basic action and one caveat but omits irreversibility, default flow behavior, and any guidance on comparing with sibling operations. It is adequate but has clear gaps.
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 coverage is 100%, so baseline is 3. The description adds meaningful semantic detail by specifying that the 'start-task' flow requires confirm:true, which goes beyond the schema's generic boolean description and helps the agent set the correct value.
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 opens with 'Eliminar un flow', a specific verb and resource, and clearly distinguishes itself from flow creation, retrieval, listing, and update siblings. The additional caveat about 'start-task' doesn't muddy the core purpose.
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?
No guidance is given on when to use this delete tool versus other flow management tools. The confirm:true note is a parameter prerequisite rather than a usage-context instruction, and no alternatives or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.