Delete a OneDrive file

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

Adds recoverability ('moves to the OneDrive recycle bin') and a confirmation requirement beyond what annotations already state (destructiveHint=true). This gives the agent important behavioral context for a mutation, meeting the lowered bar set by annotations.

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, zero waste, with the action and critical safety note front-loaded. The structure is clean: what it does, where it goes, how to call it, and a safety directive.

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 delete operation with destructiveHint, it covers the essentials: the action, recoverability, how to get the ID, and the confirmation requirement. No output schema is present, but delete typically returns minimal info, so this is adequate. Missing edge cases like non-existent files aren't critical.

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 covers both params, but the description enriches them: it specifies fileId comes from list_onedrive_files and that confirm:true is required (aligning with the schema's 'REQUIRED true' description). This helps the agent construct valid calls.

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+resource: 'Delete a OneDrive item' with the key behavior of moving to the recycle bin. Clearly distinguishes from siblings like delete_drive_file by specifying OneDrive specifically, so an agent can immediately know what it's for.

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?

Provides explicit instructions: 'Pass fileId (from list_onedrive_files) + confirm:true' and emphasizes confirming with the user first. While it doesn't name alternatives or when-not-to-use, the guidance is clear and actionable for this destructive operation.

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