create-onedrive-folder

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

Annotations already indicate write (readOnlyHint=false) and potential destructiveness (destructiveHint=true). The description adds value by disclosing conflict behavior (rename, replace, fail) and that body must include 'folder{}' to create a folder. No mention of auth or rate limits, but acceptable for this tool.

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 short but front-loaded with a vague first sentence ("Create new navigation property to children for drives") that could be omitted. The tip is structured well and provides key info. It earns its place but has some 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 complexity of the input schema (many nested properties), the description covers the essential fields and conflict handling. It doesn't explain return values (no output schema) or how the tool fits with siblings, but for a creation tool with good schema coverage, it's minimally adequate.

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 80%, with many parameters described. The description adds emphasis on required 'name' and 'folder' fields and the conflictBehavior parameter, which are critical for correct invocation. This adds meaningful guidance beyond the schema alone.

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's tip clearly states it creates a folder inside a drive item. The first line is technical ("Create new navigation property to children for drives") but the tip clarifies the action. It doesn't explicitly differentiate from sibling tools like 'create-drive-item-share-link' or 'copy-drive-item', but the folder creation context is distinct enough.

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 explicit instructions: body must include 'name' and 'folder' fields, and how to use @microsoft.graph.conflictBehavior with options (rename, replace, fail). No alternatives or when-not-to-use are given, but for a simple folder creation tool this is adequate.

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