Create OneDrive Folder

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

With no annotations, the description carries the full burden. It usefully discloses the delegated Files.ReadWrite permission and target location, but it omits behavior around name conflicts (despite the schema enum), return values, and error conditions.

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 core description is concise and front-loaded with the action and target. The Chinese intent line adds a bit of length but serves a clear multilingual purpose. No redundant filler.

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 create operation with a well-described schema, the description is serviceable. However, without an output schema, it does not mention return object shape, and it lacks explicit sibling differentiation or conflict-behavior caveats, leaving moderate gaps.

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% with descriptions for all parameters, so the baseline is 3. The description adds context about root/parent location that maps to parentItemId, but it does not add significant syntax or format details beyond the schema.

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 a specific verb ('Create') and resource ('folder in the signed-in user OneDrive root or under a parent folder'), clearly distinguishing it from sibling tools like mail_create_folder, contacts_create_folder, and sharepoint_create_drive_folder by scope.

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?

It clearly states the intended context (signed-in user's OneDrive, root or parent folder) and the required permission. However, it does not explicitly mention when not to use it or contrast with sharepoint_create_drive_folder, so it falls short of a 5.

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