Delete a named dataset from a scenario to remove unwanted test data. Specify the scenario ID and dataset name to clean up project resources.
Remove a named scenario-data dataset.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| project | No | Path to the project root (same folder the side panel connects to). Defaults to the EASYSPEC_PROJECT environment variable if omitted. | |
| scenarioId | Yes |
Changes observed during successful MCP inspections.
v1.1.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description indicates destructiveness by using 'remove', but lacks explicit warnings about permanence or cascading effects. Since no annotations exist, the description carries the full burden, and it only partially fulfills this.
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 extremely concise, consisting of a single sentence with no superfluous information. It is well-structured for a simple removal operation.
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?
The description is sufficient for a basic agent to understand the action, but lacks information about expected outcomes (e.g., success/failure behavior) or error handling. Given its simplicity, it is somewhat complete but could benefit from more detail.
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?
Only the 'project' parameter has a description; 'name' and 'scenarioId' are left implied by context. The tool name and description suggest that 'name' is the dataset name and 'scenarioId' identifies the scenario, but this is not explicitly documented.
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 (a named scenario-data dataset). It is unambiguous, though it doesn't elaborate on what a 'scenario-data dataset' specifically comprises.
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 like set_scenario_dataset or remove_flow_dataset. The description does not mention any prerequisites or conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.