Delete files

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

No annotations are provided, so the description carries the full behavioral burden for a destructive mutation. It never states whether deletion is permanent, whether directories are removed recursively, whether missing paths cause an error, or what permissions/keys are required — all critical for an irreversible 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?

A single front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of the behavioral detail noted elsewhere rather than being genuinely complete.

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 seven-parameter destructive tool with no annotations and no output schema, the description omits the information an agent most needs: irreversibility, recursion over directories, auth/override behavior, and error conditions. What exists is accurate but far from sufficient.

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 coverage is 71%, so the schema already documents most parameters including the 'names relative to root' semantics. The description's phrase 'under a root directory' loosely frames the root/files pairing but adds no syntax, path-format, or override-precedence detail beyond the schema.

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?

States a specific verb (delete) and resource (files/directories) with scope ('under a root directory') and batch cardinality ('one or more'). It is clearly distinguishable from read-oriented siblings like files_list/files_read, though it never explicitly contrasts with the closer files_rename or files_copy.

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 on when to use this versus alternatives such as files_rename or files_copy, and no mention of preconditions (does the path need to exist, must it be empty for directories). The only usage signal is the word 'delete' in the title.

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