create_drive_folder

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

With no annotations provided, the description carries the full disclosure burden. It discloses the core mutation (creates a folder), the shared-drive capability, and the return format (confirmation message with folder name, ID, and link). It does not disclose auth/permission requirements, behavior on duplicate folder names, or whether the parent folder must already exist, which are meaningful gaps for a write operation with zero annotation coverage.

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 front-loaded with the one-sentence purpose, followed by clean Args and Returns sections. Every sentence earns its place, and the length is appropriate given that the schema provides no property descriptions. There is no redundant or filler content.

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 low-complexity tool (3 simple parameters, no nested objects) with no annotations and no schema descriptions, the description covers purpose, every parameter with defaults and caveats, and the return value. The remaining gaps—explicit alternative routing and auth/permission context—are moderate, so it stops just short of fully complete.

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 0%, so the description must carry the full burden, and it does. All three parameters are documented with meaning: user_google_email is marked Required, folder_name is described, and parent_folder_id is given a default ('root') plus a shared-drive usage caveat ('use a folder ID within that shared drive'). This is exactly the compensating documentation a bare schema needs.

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 first sentence states a specific verb and resource: 'Creates a new folder in Google Drive, supporting creation within shared drives.' This clearly identifies the operation and its special scope. It does not explicitly differentiate from the sibling create_drive_file, though the word 'folder' inherently sets it apart from file-creation siblings.

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?

Usage context is implied rather than stated: the description implies it is the tool for creating folders, and the parent_folder_id note gives shared-drive guidance. However, there is no explicit when-to-use or when-not-to-use guidance, and no named alternative such as create_drive_file for file creation. An agent must infer tool selection from the name and resource type.

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