create-onedrive-folder

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

Annotations already indicate destructiveHint=true, and the description confirms creation of a folder. The tip adds useful detail about conflict behavior. However, it lacks disclosure of auth requirements, rate limits, or failure behavior. 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?

The first sentence is confusing and adds little value. The tip is concise and helpful. Overall, the description could be shorter and more focused.

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?

The description covers essential usage (required body fields, conflict handling), but does not explain the return value (no output schema) or provide completeness for optional body fields. Adequate but not thorough.

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 high (83%), but the description adds critical info: body must include name and folder fields, and mentions conflictBehavior. This goes beyond the schema's generic property descriptions, making parameter semantics clearer.

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 initially says 'Create new navigation property to children for drives' which is vague, but the tip clearly states 'Creates a new folder inside the specified drive item.' This effectively communicates the purpose. While not explicitly differentiating from siblings, it is clear enough among the many drive-related tools.

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 guidance on required body fields (name, folder) and conflictBehavior options, but does not explicitly state when to use this tool versus alternatives like upload or copy. No prerequisites or permissions are mentioned.

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