delete_file

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

With no annotations, the description discloses a useful behavioral constraint (files only) but omits mentioning that deletion is permanent or irreversible, and does not address permissions or side effects, leaving a moderate transparency gap for a destructive operation.

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 concise and front-loaded with the main action. The bilingual repetition is a minor addition but does not introduce redundancy for the intended audience, and every sentence serves a clear purpose.

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 single-parameter deletion tool with an output schema available, the description adequately covers the purpose, the file-only constraint, and the alternative tool, making it contextually complete without needing to explain return values.

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 already provides a complete description and examples for the 'path' parameter, including the file-only restriction. The tool description repeats this without adding new parameter semantics, so a baseline score of 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?

The description clearly states the tool's purpose with a specific verb and resource ('Delete a specific file'), and explicitly differentiates it from siblings by noting it only works on files, not directories, and directs users to the 'delete' tool for uncertain cases.

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 explicit when-to-use guidance by stating 'Only works on files, not directories' and naming the 'delete' tool as an alternative when the path type is unknown, making the decision between tools clear.

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