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

Annotations already declare destructiveHint: true and readOnlyHint: false, establishing the safety profile. The description adds the useful constraint that only empty folders can be deleted, which is beyond the annotations. However, it omits mention of the confirm parameter and whether deletion is permanent or moves to trash.

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?

A single concise sentence that conveys the essential purpose without redundancy. Every word earns its place, making it highly scannable.

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 delete tool with a full output schema and annotations, the description is largely sufficient. It covers the core action and an important constraint (empty folder). However, it could optionally mention the confirm requirement and the nature of deletion (permanent vs. trash) for added completeness, though these are partly covered by schema.

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?

The schema fully documents both parameters (path with 'Absolute path' and confirm with 'Must be true to delete'), so the description adds no additional parameter meaning. With 100% schema coverage, the baseline of 3 applies without any extra compensation.

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 (deletes) and the target (a file or empty folder on OneDrive), using a specific verb and resource. It distinguishes from sibling tools like onedrive_write_file or onedrive_move_file by the deletion action and the OneDrive scope.

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 guidance is given on when to use this tool versus alternatives, nor are there any exclusions or prerequisites. The only implicit usage is the destructive action itself, but the description does not mention the required confirm flag or contrast with non-destructive options.

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