onedrive_delete_file

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

With no annotations, the description carries the full burden. It usefully discloses that deletion is PERMANENT and that only EMPTY folders can be deleted, which is valuable behavioral context. However, it omits whether confirmation is required, whether deletion is recoverable, permission requirements, or what happens if the folder is non-empty.

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 sentence, front-loaded with the verb 'Permanently deletes', and the key constraint (EMPTY folder) is highlighted in caps. Zero waste.

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 no annotations and no output schema, the description over-relies on the one-line statement. It covers the permanence and the empty-folder constraint, but lacks guidance on prerequisites, error conditions, or alternatives. Adequate but with gaps.

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?

Parameter count is 0, so the baseline is 4. The description does not need to explain parameters, and correctly omits any parameter discussion.

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 (deletes) and resource (file or EMPTY folder) with clear scope (inside the OneDrive folder synced on this Mac). Distinct from siblings like onedrive_move_file, onedrive_write_file, and gdrive_delete_file.

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?

Implies usage (delete something in OneDrive) but does not state when to use this vs onedrive_move_file to a trash location, or vs gdrive_delete_file. No exclusions or prerequisites mentioned.

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