drive_create_folder

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

No annotations are provided, so the description carries the full burden. It does disclose one meaningful behavioral trait — that intermediate folders in the path are created ('nested') — but it omits critical mutation semantics: what happens if the folder already exists, whether the call is idempotent, and what permissions are required. 'Returns id' adds nothing since an output schema already exists.

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?

Two short sentences, no filler, with the core action front-loaded. Nothing is wasted, though the second sentence is redundant given the output schema.

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?

Because an output schema exists, the description need not explain return values. However, for a mutating filesystem tool with zero annotations and an undocumented path parameter, the description should say more about path formatting and existing-folder behavior to be sufficient 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?

Schema coverage is 0% — the single 'path' parameter has no description in the schema at all. The word 'nested' implies a multi-segment path but the description never specifies the separator convention, whether a leading slash or root-relative form is expected, or an example. It partially compensates for the coverage gap but leaves the most important format question unanswered.

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 names a specific verb and resource ('Create a ... OneDrive folder path') and adds the scoping qualifier 'nested', which distinguishes it from the sibling drive_list and drive_move as well as from the mail_* folder tools. It is clear what the tool does, though it doesn't explicitly name the sibling it contrasts with.

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?

There is no statement of when to use this tool versus alternatives such as drive_move or mail_create_folder (which handles mail folders), and no prerequisites or exclusions are given. The agent must infer from the name alone that this is the folder-creation entry point for OneDrive.

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