delete_file

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It correctly identifies the tool as destructive and mentions the safety confirmation feature. However, it omits critical details such as whether the deletion is permanent, if files can be recovered, or required permissions.

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 extremely concise (seven words) and front-loaded. Every word is meaningful and earns its place, with no redundancy or fluff.

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?

Given the tool's simplicity (two parameters, obvious deletion action) and the existence of an output schema documenting return values, the description is fairly complete. However, it could improve by explicitly stating that deletion is permanent and irreversible.

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 input schema has 100% coverage (both parameters have descriptions). The description adds minimal meaning beyond the schema—'requires confirmation' reinforces the confirm parameter's role. The schema already documents that confirm 'Must be True to actually delete (safety feature)', so the description does not significantly enhance parameter understanding.

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 'Delete a file (requires confirmation)' clearly states the action and resource, distinguishing it from siblings like copy_file, read_file, and write_file. The verb and resource are specific 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?

The description hints at a usage guideline by mentioning 'requires confirmation', indicating that the confirm parameter must be set to True to perform deletion. However, it does not provide guidance on when to use this tool versus alternative deletion methods (e.g., moving to trash) or any prerequisite conditions.

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