Delete file

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

With no annotations available, the description must carry the full burden of behavioral disclosure. It only states 'Delete' without explaining recursive behavior for directories, irreversibility, permission requirements, or side effects. This is a significant 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 a single sentence and is not verbose, but it is under-specified rather than concise. There is no structure or front-loading of critical information beyond the basic operation. It could be more informative without becoming lengthy.

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 tool with two parameters and no output schema, the description is incomplete. It does not clarify whether deleting a directory is recursive, what happens if the path does not exist, or any error conditions. The agent would have to infer behavior from the name and parameters alone.

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?

Schema description coverage is 0%, and the description does not mention either parameter (app, path). It offers no explanation of what 'app' or 'path' refer to, their formats, or how they interact. The agent must guess entirely from the schema names, which is insufficient.

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 states a clear verb ('Delete') and resource ('a file or directory inside an app'), which distinguishes it from sibling delete_app. However, it does not explicitly name the alternative or contrast with other tools, so it misses the top score.

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?

There is no guidance on when to use this tool versus alternatives like delete_app or list_files. No context is given about prerequisites, safety checks, or when deletion is appropriate. The description is purely a statement of function.

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