Remove a step from an Easy Spec flow by providing its path. This tool deletes the specified step from the flow to keep Playwright test scenarios up to date.
Remove a step by its path.
| Name | Required | Description | Default |
|---|---|---|---|
| flowId | Yes | ||
| project | No | Path to the project root (same folder the side panel connects to). Defaults to the EASYSPEC_PROJECT environment variable if omitted. | |
| stepPath | Yes |
Changes observed during successful MCP inspections.
v1.1.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, and the description gives no insight into side effects, permissions, or destructive behavior beyond the obvious removal 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, short sentence that is direct and to the point, with no unnecessary words.
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?
While the purpose is clear, the description lacks essential context about how to use the parameters or what constitutes a valid step path, making it incomplete for an agent to invoke correctly.
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 description does not explain any of the three parameters (flowId, stepPath, project). The schema only has a description for project, and the tool description adds nothing to clarify the others.
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 action (remove) and the target resource (a step) with a specific method (by path). It distinguishes from sibling tools like delete_flow or update_step.
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 provided on when to use this tool versus alternatives, nor any preconditions or context for calling it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.