delete

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

The description discloses the key behavioral distinction: deleting without 'permanently' sends items to trash, while 'permanently=True' skips trash. However, it does not mention potential consequences like irreversible loss, permission requirements, or how folders are handled (e.g., recursive deletion), leaving gaps 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 brief and well-structured: a one-line purpose followed by an Args block with two clear entries. No filler, repetition, or unnecessary detail.

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?

The description covers the essential semantics of a two-parameter delete operation with no output schema. It clearly communicates the trash vs. permanent behavior, but could be enriched by explicitly addressing folder deletion and the relationship to trash management tools like empty_trash and restore_from_trash.

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?

With zero schema description coverage, the description compensates well. 'Path' is given a concrete example, and 'permanently' is defined as 'skip trash and delete permanently with Default False', adding meaningful context beyond the schema's type and 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 opening line 'Delete a file or folder' is a specific verb+resource statement that clearly distinguishes this tool from siblings like copy, move, or rename. The parameter details reinforce the delete action without ambiguity.

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 provides no guidance on when to use this tool versus alternatives such as list_trash, restore_from_trash, or empty_trash. It does not mention the default trash behavior as a usage consideration or explain how this tool fits into the trash lifecycle.

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