Create SharePoint Library Folder

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

No annotations exist, so the description carries the full burden. It discloses the permission requirement and the allowed creation locations (root or parent folder). However, it does not mention conflict behavior (which defaults to rename) or failure semantics, leaving some behavioral aspects undocumented.

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 front-loaded with the core purpose, followed by a useful permission note. The Chinese translation duplicates the first sentence but serves localization needs. Overall, it is compact with minimal waste.

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 (4 parameters, no output schema), the description provides the essential action, permission, and scope. It does not explain return values, but that is not required when no output schema exists. Combining with the schema gives sufficient information for correct invocation.

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 provides descriptive text for all four parameters (100% coverage), so the baseline is 3. The description adds no substantial parameter meaning beyond the schema; the mention of 'root or parent folder' is redundant with parentItemId's already-documented default.

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 ('SharePoint document library'), and further scopes it to 'root or parent folder'. This clearly differentiates from sibling tools like drive_create_folder (which targets OneDrive) and sharepoint_create_list_item (which creates list items).

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 stating the operation is for SharePoint document libraries and includes a required permission (delegated Files.ReadWrite.All). It does not explicitly name alternatives or exclusions, but the context is strong enough for an agent to infer when to use this tool.

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