onedrive_move_file

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses that the tool mutates state and that OneDrive syncs the change, but it omits critical details such as required permissions, overwrite behavior, error handling, and whether the move is reversible.

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 short and front-loads the main action. The trailing clause about OneDrive syncing the change is somewhat vague and appears truncated, but overall the structure is efficient and non-repetitive.

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 file mutation tool with no annotations and no output schema, the description is incomplete. It does not explain how source and destination are specified, rename semantics, permissions, or what happens when the target already exists.

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 has zero parameters and 100% description coverage, so the baseline is 4. The description does not need to add parameter meaning because there are no parameters to document, though the empty schema itself is unusual for a move/rename operation.

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 uses specific verbs (moves or renames) and a clear resource (file or folder inside the OneDrive folder synced on this Mac). It distinguishes the tool from unrelated siblings, though it does not explicitly differentiate it from other OneDrive file operations like onedrive_delete_file or onedrive_write_file.

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 when-to-use guidance or alternatives are provided. The description implies that this tool is for moving or renaming OneDrive files, but it does not tell the agent when to choose it over siblings such as onedrive_write_file or onedrive_delete_file.

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