delete_file

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

No annotations are provided, so the description must fully explain the behavior. It merely states the action without disclosing that deletion is typically permanent, what happens if the path does not exist, whether directory deletion is supported, or if special permissions are required. This is a destructive operation with minimal behavioral disclosure.

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, brief sentence with no wasted words. It is front-loaded and direct, making it easy to parse and immediately understand the tool's core function.

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?

As a destructive mutation tool with no annotations, the description should provide more context. While an output schema exists, the description omits critical behavioral details such as irreversibility, error handling, and whether directories can be deleted. The side effects of the operation are not fully conveyed.

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 has one parameter, path, with 0% description coverage. The description only mentions 'the given path' without adding guidance on path format (absolute vs relative), type constraints, or error conditions. The description fails to compensate for the lack of schema-level parameter documentation.

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 uses the specific verb 'delete' and identifies the resource 'the file at the given path', clearly distinguishing it from sibling tools like read_file, write_file, and update_file. The scope is precise and unambiguous.

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 such as write_file or update_file, nor are any scenarios or prerequisites mentioned. The tool could be used for permanent file removal, but the description does not indicate when that is appropriate.

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