Move OneDrive Folder

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

Annotations confirm readOnlyHint=false (modification) and destructiveHint=false. The description adds the behavioral note about user confirmation and raises ValueError for invalid IDs, enhancing transparency beyond annotations.

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 and well-structured with an emoji, brief intro, and clearly separated Args, Returns, and Raises sections. No unnecessary words.

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 operation with output schema and annotations, the description covers purpose, parameters, return type, and errors. Lacks details on potential conflicts or permission needs, but openWorldHint partially addresses side effects.

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%, but the description provides clear explanations for each parameter under Args (folder_id, destination_folder_id, account_id), adding meaning beyond the raw type string.

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 tool moves an OneDrive folder to a different parent, using a specific verb and resource. It distinguishes from sibling tools like folder_rename and file_move by focusing on folder hierarchy change.

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 mentions 'requires user confirmation recommended' but does not explicitly state when to use this tool versus alternatives like file_move or when not to use it. No guidance on prerequisites or conditions.

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