delete_file

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

With no annotations provided, the description carries the full transparency burden. It discloses the key behavioral distinction between trash (default, non-permanent) and permanent deletion (irreversible), which is essential. However, it does not mention whether trashed files can be restored or any permission requirements.

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 that front-loads the core behavior and includes the critical default. No filler words.

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 delete operation, the description covers the primary behaviors and outcomes. It doesn't describe return values or recovery from trash, but these are not essential given the tool's simplicity and the context from sibling tools.

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 covers the 'permanent' parameter with a detailed description, and the tool description reinforces the default. The 'id' parameter is self-explanatory in context. The description adds minimal parameter semantics beyond the schema, but the 50% schema coverage is partially compensated by the explicit default.

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 function: moving a file to trash or deleting it permanently, with a clear default. The verb+resource is specific, and the mention of 'file' distinguishes it from folder deletion tools in the sibling list.

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 implies the tool is for deleting files but does not explicitly state when to use it versus alternatives like delete_folder. It provides context about the default behavior but lacks exclusions or alternative guidance.

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