Create Drive Folder

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

Annotations already indicate a non-read-only operation, so the description is not required to state mutation. It adds the shared drive support detail, which is a useful behavioral nuance. However, it does not disclose other traits like name conflict handling, auth requirements, or response format, so it provides only partial transparency.

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 a single, front-loaded sentence that efficiently states the core purpose and the shared drive differentiation. No wasted words.

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 a complete schema and output schema present, the description covers the essential purpose and shared drive support. It does not elaborate on edge cases or prerequisites, but the overall level is adequate for a straightforward folder creation tool, leaving minor gaps.

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 input schema covers 100% of the parameters with descriptions, including the shared drive note for parent_folder_id. The tool description does not add additional parameter-level meaning beyond what the schema already provides, so the baseline of 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?

The description clearly states 'Creates a new folder in Google Drive' which is a specific verb+resource+scope. It also adds the shared drive support, distinguishing it from sibling tools like create_file or copy_drive_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 description implies when to use by naming the resource (folder) and specifically notes support for shared drives, which gives context for the parent_folder_id use case. However, it does not explicitly state when not to use it or name alternatives like create_file for files.

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