Delete

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

The description goes beyond the destructiveHint annotation by explaining what actually happens: the item 'moves to deleted state' and 'can be restored from Dropbox for the retention window.' This gives the agent useful context about recoverability and the temporary nature of the deletion.

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?

Two short sentences with no filler. The core action is front-loaded, and the destructive consequence is stated immediately after, making the most important safety information prominent.

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 one-parameter destructive tool with no output schema, the description covers the action, the scope (recursive deletion), the state change, and recoverability. This is sufficient for an agent to correctly select and invoke the tool.

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 already fully documents the 'path' parameter with an example and root behavior. The description adds semantic value by clarifying that a folder path will delete its contents as well, which is not explicit in the schema description.

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'), the target resource ('a file or folder'), and an important scope detail ('and its contents'). It is unambiguous and clearly distinguishes this tool from the sibling file/folder operations like move, copy, upload, and 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 purpose itself defines when to use the tool: when a file or folder should be removed. It does not explicitly discuss alternatives, but none of the sibling tools perform deletion, so no exclusionary guidance is needed. The destructive warning reinforces that this is the deletion tool.

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