delete_file

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

The description discloses policy checks and optional backup, adding behavioral context beyond a simple delete. However, with no annotations, it still lacks details on permissions, error handling, or reversibility.

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?

A single sentence of 10 words, front-loading the verb and resource. Every word earns its place; no redundancy.

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?

The description covers purpose and one behavioral trait, but ignores parameter details and return values. Given the presence of an output schema, it still fails to explain what the tool returns or how to use the parameters.

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?

With 0% schema description coverage, the description must explain parameters (path, ctx). It does not mention either, leaving the agent without guidance on their meaning or format.

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 deletes a single file, with specific behavior: policy checks and optional pre-delete backup. This distinguishes it from sibling tools like restore_backup or write_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 explicit guidance on when to use this tool versus alternatives. While the description implies a use case (deleting with checks/backup), it does not specify when not to use it or compare with siblings like edit_file or execute_command.

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