Delete a file on a remote server via SFTP. Provide the full path to the file to remove it.
Удалить файл на удалённом сервере через SFTP
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Полный путь к файлу для удаления |
Changes observed during successful MCP inspections.
v1.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations and the description doesn't disclose whether deletion is permanent, requires elevated permissions, or fails on non-existent files. Only the operation is stated without rich behavioral context.
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?
One short, front-loaded sentence with zero waste.
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 operation with no annotations and no output schema, the description omits critical context: required connection state, error conditions, and deletion irreversibility.
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?
Single parameter with 100% schema coverage; description's mention of 'full path' aligns with schema but adds no extra syntax details, which is acceptable for one param.
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 specific verb (delete) and resource (file on remote server via SFTP), clearly distinguishing from siblings like sftp_write_file or sftp_read_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?
No context given about when to use this versus alternatives, prerequisites (e.g., must be connected via sftp_connect), or whether it works on directories.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.