Move OneDrive Item

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

With no annotations provided, the description carries the full burden. It usefully discloses the required delegated permission and the mutation implied by 'move.' However, it does not mention side effects like the item disappearing from the source folder or potential changes to sharing links, though these are somewhat inherent in the operation.

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 two sentences long, front-loaded with the primary English purpose and permission requirement, followed by helpful multilingual intent aliases. Every sentence adds value, with no wasted 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?

Given the tool's simplicity (2 parameters, no output schema), the description covers the core operation and permission context. It lacks an explicit statement about return values, but for a move action, the outcome is generally clear. The multilingual aliases enhance completeness for Chinese-speaking intents.

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 coverage is 100% as both itemId and newParentItemId have concise descriptions. The description adds no additional parameter detail beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 a file or folder in the signed-in user's OneDrive to a new parent folder. It uses a specific verb and resource, and differentiates from siblings like drive_copy_item and drive_rename_item by explicitly indicating relocation.

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 provides clear context by specifying the scope (signed-in user's OneDrive) and a prerequisite (requires delegated Files.ReadWrite). It does not explicitly mention alternatives or exclusions, but the action is unmistakable, and the Chinese intent aliases help recognize relevant user requests.

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