delete_itemDelete a file or directory from the Filen cloud. By default the item is moved to the trash; set permanent=true to delete it permanently.
Delete a file or directory from the Filen cloud. By default the item is moved to the trash; set permanent=true to delete it permanently.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Absolute cloud path of the item to delete | |
| permanent | No | If true, delete permanently instead of moving to trash |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already flag destructiveHint=true, but the description adds the crucial non-obvious behavior that deletion is recoverable by default via trash and only irreversible with permanent=true. That is real value beyond the structured fields.
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 tight sentences with the scope stated first and the recoverability caveat immediately after; nothing wasted.
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 two-parameter destructive tool with an existing output-schema-free surface, this covers scope and the trash/permanent distinction. Minor gaps remain on error conditions, but nothing critical is missing for correct invocation.
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% and the schema already documents both path and permanent including defaults, so the description largely restates it. Baseline 3 is appropriate.
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?
States a precise verb and resource ('Delete a file or directory') scoped to 'the Filen cloud', making it clearly distinct from siblings like write_file or upload_file.
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?
Usage is implied by the destructive verb, but the description never states when to prefer deletion over other operations or what happens if the path is invalid. No explicit alternative or precondition is named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.