create-onedrive-folder

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

Annotations indicate this is a write/destructive operation, and the description confirms by stating it creates a folder. The tip adds behavioral detail about conflict resolution that is not in the schema. No contradictions 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?

The description is short but the first sentence is jargon-heavy and not front-loaded. The tip is helpful. Could be more concise and direct.

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?

With 5 parameters (3 required), nested body, and no output schema, the description lacks details about driveId and driveItemId parameters and does not describe the response. It covers the essential body requirements but is incomplete for a complex tool.

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%, so baseline is 3. The description adds the requirement for name and folder fields in the body and mentions conflictBehavior, which is not in the schema. This adds some value but does not explain other body properties.

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 creates a new folder inside a specified drive item, with the tip reinforcing the purpose. The first sentence is somewhat vague but the tip clarifies. Distinguishes from siblings like copy-drive-item or delete-onedrive-file.

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 mentions conflictBehavior options but does not provide explicit when-to-use guidance or alternatives. Usage context is implied but not explicitly stated.

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