Move SharePoint Library Item

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

No annotations are provided, so the description carries the full burden of disclosing behavioral impact. It only states the action and scope; it does not mention side effects such as broken sharing links, overwrite behavior, permission requirements, or how the item's metadata/version history is affected. For a mutating operation, this is a significant gap.

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?

Two short sentences: the core action is front-loaded in English, followed by Chinese translations/examples. No wasted words, and the multilingual hint adds utility for Chinese-language intents without bloating the description.

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 three required parameters and no output schema, the description covers the basic 'what' and 'where.' However, it lacks behavioral details such as error conditions, required permissions, or return values, and since there are no annotations to compensate, the description is only minimally complete for real-world use.

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 already describes all three parameters (source item ID, drive ID, destination parent folder ID) with 100% coverage, giving a baseline of 3. The description adds an important semantic constraint that the destination folder must be in the same document library, which helps the agent understand the relationship between parameters and reject invalid destinations.

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?

Clear and specific: 'Move a file or folder to another folder in the same document library.' It names the verb (move), object (file/folder), and scope (same document library), which distinguishes it from copy, rename, or delete operations. The Chinese examples reinforce the intended use case.

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 does not explicitly compare against sibling tools like drive_move_item or sharepoint_copy_drive_item. It implies the use case (reorganizing files within a SharePoint library) and includes the constraint 'same document library,' but lacks explicit 'use this when' or exclusion criteria for alternative tools.

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