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

Annotations already declare destructiveHint=true and readOnlyHint=false, covering the safety profile. The description adds no extra behavioral context beyond the action itself, such as the confirmation requirement or potential side effects. However, it does not contradict the annotations, and the annotations carry the important warning, so a neutral score is appropriate.

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?

The description is a single, front-loaded sentence that directly conveys the tool's purpose with no filler or redundant information. Every word earns its place.

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 move/rename operation, the description is adequate but minimal. It omits the critical behavior that 'confirm' must be true to execute the move, which is documented only in the schema. While the output schema exists and annotations handle safety, the description could provide a bit more context about the confirmation requirement and the difference between moving and renaming.

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 input schema provides descriptions for all three parameters, including 'confirm' ('Must be true to move'). The tool description adds no additional parameter meaning beyond what the schema already covers, so the baseline score of 3 applies.

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 ('Moves or renames'), the resource ('a file/folder'), and the scope ('within OneDrive'). It effectively distinguishes this from sibling tools like onedrive_delete_file or onedrive_write_file by specifying the relocation/rename purpose.

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 provided on when to use this tool versus alternatives. The description does not mention situations like renaming versus moving, or when to prefer this over onedrive_write_file. It relies entirely on the tool's name and the verb 'moves or renames' to imply usage.

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