delete

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

With no annotations provided, the description carries the full burden. It crucially discloses the soft-delete nature ('moves to trash'), which is vital safety information. However, it omits whether this requires specific permissions, if there's a recovery window, or what happens to shared links/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?

Single 9-word sentence with zero waste. Every word earns its place: action (Delete), target (file or folder), scope (Dropbox), and critical behavioral detail (moves to trash). Perfectly front-loaded and appropriately sized for the tool's simplicity.

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 single-parameter deletion tool with no output schema, the description is sufficiently complete. It covers the operation, target, domain, and trash behavior. Could mention return value or error conditions (e.g., path not found), but adequate for complexity level.

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 100% (path is documented as 'Path to delete'), so the baseline is 3. The description adds minimal parameter-specific semantics beyond the schema, though it implies the path refers to files/folders in Dropbox context.

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?

Excellent clarity with specific verb 'Delete', resource 'file or folder', and scope 'in Dropbox'. The '(moves to trash)' parenthetical distinguishes the exact semantics from permanent deletion, clearly differentiating it from potential alternatives.

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 versus the 'move' tool (which could theoretically be used to relocate to trash) or prerequisites like file existence. The trash note provides implicit behavioral guidance but lacks explicit when-to-use context.

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