delete_file

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

The description discloses the default soft-delete behavior and the skip_soft_delete parameter for permanent deletion, which is helpful. However, it does not mention side effects (e.g., folder deletion cascading, recoverability), and no annotations exist to supplement behavioral traits.

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 front-loaded with the verb and resource, with zero waste. Every word serves a purpose.

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 deletion tool with 3 parameters and no output schema, the description covers core purpose and default behavior but omits error cases, return values, folder handling, and permission requirements. It is adequate but not comprehensive.

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 67% (path and skip_soft_delete have descriptions, unlink lacks one). The description adds meaning for skip_soft_delete but not for unlink, and path is self-explanatory. It partially compensates but leaves one parameter undocumented.

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 action ('delete') and resource ('remote files/folders'), and distinguishes its default behavior (soft-delete to trash) from other sibling tools like rename, copy, upload, etc.

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 (e.g., when to prefer delete over move to trash, or prerequisites like write permissions). The usage is implied but not contextualized.

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