move-rename-onedrive-item

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds minimal extra context beyond stating the ability to move/rename in one request. It does not discuss side effects like broken links or 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 mostly concise with a clear tip. However, the first sentence 'Update the navigation property items in drives' is generic and adds little value; it could be replaced to improve conciseness.

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 specific purpose and the presence of annotations and schema, the description covers the essential move/rename operations. It lacks mention of required driveId and driveItemId paths, but these are in the schema. Minor gap in explaining response or error handling.

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 description maps usage directly to key parameters: parentReference for moving and name for renaming, adding meaning beyond the schema. With 80% schema coverage, it compensates by highlighting critical parameters in context.

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 and/or renames a file or folder in OneDrive, with specific verb-resource combinations. It distinguishes from siblings like copy-drive-item and delete-onedrive-file by focusing on move/rename operations.

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 tip provides clear guidance on when to use: provide parentReference.id to move, provide new name to rename, and both can be combined. However, it does not explicitly mention when not to use (e.g., use copy instead of move) or list alternatives.

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