Create OneDrive Folder

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

Annotations already indicate non-read-only and non-destructive. The description adds behavioral traits: creates at root or child, requires user confirmation, raises ValueError for invalid inputs. No contradiction with 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?

Description is concise with clear sections (Args, Returns, Raises) and no redundant information. The emoji and user confirmation note are front-loaded. Could remove the 'Args:' prefix since schema already defines, but it's still efficient.

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 moderate complexity (3 params, output schema exists), the description covers creation behavior, parameter semantics, return value, and error cases. Missing details like behavior on duplicate names or permissions, but overall sufficient for an agent.

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?

Input schema has 0% parameter descriptions, so the description compensates by explaining the purpose and constraints of each parameter (name, account_id, parent_folder_id with default None). Could include validation rules or formatting, but still adds significant value.

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 verb (create), resource (OneDrive folder), and scope (root or child of existing folder). It distinguishes itself from sibling tools like file_create and emailfolders_create by specifying it's for OneDrive folders.

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 provide explicit guidance on when to use this tool versus alternatives (e.g., folder_move, folder_rename) or when not to use it. No reference to sibling tools.

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