drive_create_folder

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

The annotations already communicate that this is a mutating, open-world operation (readOnlyHint=false, openWorldHint=true), so the description does not need to restate that. It adds some value by specifying the return payload (id, name, webViewLink), but it does not disclose potential side effects, failure modes, or permissions beyond what the schema and annotations imply.

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, direct, and front-loaded with the primary action. Every sentence serves a purpose: the first states the operation and resource, and the second specifies the return format. There is no filler or repetition of schema information.

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 create-folder tool, the description covers the core operation and the return value, and the schema and annotations together fill in parameters and mutation intent. The main missing piece is usage guidance around when to choose this over sibling creation tools, but the tool is still sufficiently callable in most straightforward cases.

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?

The schema description coverage is 0%, and the description does not compensate by explaining parameters like parent_folder_id or its default behavior. Although the schema properties have their own descriptions, the tool description itself provides no parameter-level semantic guidance, which is a clear gap for a create operation with a parent folder option.

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 states a clear, specific action: 'Create a new folder in Google Drive.' It names the exact resource (folder) and verb (create), and the return value specification further clarifies what the tool does. It is easily distinguished from sibling tools like drive_upload_file or docs_create_document.

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 description provides no guidance on when to use this tool versus alternatives such as drive_upload_file or sheets_create_spreadsheet. There are no exclusions, prerequisites, or conditions, leaving the agent to infer suitability from the name alone.

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