Creates a new folder in the current location or under a specified parent path, letting AI agents organize Google Drive content through Android app operations.
Create a new folder in the current location (or in path).
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name of the new folder. | |
| path | No | Parent folder ("A/B" relative, "/A/B" from My Drive, "/" = My Drive root); default: the current location. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden yet only says a folder is created. It is silent on what happens if the name already exists, whether this is idempotent, whether parent paths must exist, and on permission/error behaviour for a mutating operation.
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?
A single short sentence with the action front-loaded and the location qualifier immediately after; nothing is wasted.
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?
For a simple two-parameter create operation with a fully documented schema and no output schema, the description covers enough to call it correctly. The main missing piece is collision/overwrite semantics, which is a modest gap for a create 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 description coverage is 100%, with both `name` and `path` documented including the relative/absolute path syntax and defaults. The description only restates the `path` fallback, adding nothing beyond the schema, so the baseline 3 applies.
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?
States a specific verb and resource ("Create a new folder") plus the default location, which is unambiguous. It does not explicitly distinguish itself from near-neighbours like drive_upload_folder or drive_create_doc, so it stops short of a 5.
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 parenthetical "(or in ``path``)" and "current location" imply usage in the context of the drive_cd/drive_location navigation model, but there is no explicit when-to-use, when-not-to-use, or named alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.