Move File

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description's mention of moving and returning an updated object aligns without contradiction. It adds value by recommending user confirmation, but does not detail side effects like permission changes.

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 concise, using an emoji for quick recognition, and well-structured with Args and Returns sections. Every sentence is informative and 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?

Given the presence of an output schema, the description appropriately notes the return type. It covers the main aspects of the operation, though it could mention scope (OneDrive) and authentication requirements more explicitly.

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 description coverage is 0%, so the description carries full burden. It lists all three parameters with meaningful labels ('file ID', 'destination folder ID', 'Microsoft account ID') that add context beyond the schema's property names.

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 explicitly states 'Move a file to a different folder' and 'Moves a file to a different parent folder within OneDrive', providing a clear verb+resource combination. It distinguishes from siblings like file_copy or file_delete by specifying 'move' and targeting a different folder.

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 includes 'requires user confirmation recommended', indicating a precondition. However, it does not explicitly contrast with folder_move or specify when not to use this tool. The context is clear enough for the intended use case.

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