delete_file

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full transparency burden. It helpfully discloses that a backup is created in .mcp-backups/ before deletion and that directories cannot be deleted. However, it does not explain restore procedures, permissions required, or behavior for non-existent files.

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 concise sentences convey all essential information: the action, the backup behavior, and a key limitation. No filler or redundant 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 simple one-parameter destructive tool, the description covers purpose, backup behavior, and a critical limitation. The absence of an output schema makes return-value documentation unnecessary, and the backup note mitigates the need for an explicit irreversibility warning.

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 schema description covers 100% of the parameter (filepath) and includes 'relative to project root or absolute.' The tool description adds no additional parameter-level detail, so it relies on the schema's existing 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 tool's action (delete a file) and its scope within the project. It also explicitly notes that directories cannot be deleted, distinguishing it from move_file or other file operations.

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 implies the tool is for files only, since it states 'Cannot delete directories.' However, it does not explicitly compare to sibling tools like move_file or edit_file, nor does it state when to use this over alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.