Remove files or directories from your workspace to manage storage and organize projects. Specify the path to delete unwanted items.
Delete a file or directory
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to delete |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of disclosing behavioral traits. It only states 'delete', implying a destructive action, but does not describe reversibility, error handling, or side effects like recursive deletion of directories. More details are needed.
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 sentence that conveys the core functionality without extraneous information. It is appropriately concise for a simple tool, though slightly under-specified in 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?
For a basic delete operation with one parameter and no output schema, the description is minimally adequate. It does not specify return behavior or confirmation messages, but the tool's simplicity partially compensates. Still, missing context on success/failure outcomes.
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 input schema has 100% coverage and one parameter described as 'Path to delete'. The tool description adds no additional meaning beyond what the schema provides. Baseline of 3 is appropriate given high schema coverage.
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 verb 'delete' and resource 'file or directory', making the tool's purpose immediately understandable. However, it does not differentiate from sibling tools that might perform similar operations, but given the unique name, clarity is sufficient.
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 provides no guidance on when to use this tool vs alternatives. There is no mention of prerequisites, fallback options, or conditions under which deletion might fail. Agents receive no context for decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.