Delete File

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

While annotations provide destructiveHint=true, the description contradicts the schema by stating confirmation is always required, yet the 'confirm' parameter is optional with default false. This misrepresentation lowers transparency.

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 sentences, no fluff, with an effective warning. 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?

The description covers the core behavior but lacks details on prerequisites, error conditions, or the output. The contradiction with the confirm parameter also reduces completeness.

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 0% and the description only implicitly references the 'confirm' parameter. It does not explain 'file_id' or 'account_id', leaving their meaning ambiguous.

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 the resource ('OneDrive file or folder'), distinguishing it from sibling tools like file_copy, file_move, 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?

The description warns about permanence and user confirmation, but does not explicitly guide when to use this tool versus the sibling 'folder_delete' tool, which could cause confusion.

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