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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description goes well beyond them: it discloses that the file bypasses Trash, that deletion syncs to the cloud, that folders with contents are refused with an item count, and that Files-On-Demand restoration causes an honest failure report rather than false success. This is unusually rich behavioral context.

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?

Front-loads the destructive scope and the Trash/cloud-sync distinction, then the refusal rules, then the confirm convention, then the edge-case behavior. Every sentence carries non-redundant information; nothing could be dropped without losing an agent-relevant fact.

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?

An output schema exists, so return values need not be described. For a two-parameter destructive tool, the description covers scope, refusals, confirmation flow, and failure reporting, leaving no gap an agent would need to guess at.

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%, so the schema already documents both parameters. The description adds real meaning beyond it by explaining confirm's preview-vs-delete semantics and that path must come from a OneDrive listing/search tool, which the schema's bare 'Absolute path' line does not convey.

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) scoped to the local OneDrive folder, and distinguishes itself from siblings like gdrive_delete_file by naming the sync target. An agent can tell exactly what this does without opening the schema.

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?

Explicitly routes the agent to onedrive_list_files or onedrive_search_files to obtain the path, defines the preview-vs-confirm calling convention, and states two refusal conditions (non-empty folder, path outside OneDrive). When-to-use and when-not-to-use are both covered.

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