Create Drive Folder

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false. The description adds the shared drive support context, which is a useful behavioral nuance not captured by annotations. However, it does not disclose other potential traits such as permission requirements, error behavior, or whether the operation is reversible, so it offers limited additional 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, concise sentence that immediately conveys the action and object. It avoids redundancy and is appropriately front-loaded.

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?

Given the simple create operation, the schema (which documents all parameters, including the parent_folder_id default and shared drive usage), and the presence of an output schema, the description is fairly complete. It adds the key contextual detail of shared drive support. A slight gap is the lack of explicit mention of default behavior in My Drive, but that is covered by the parent_folder_id default, so a 4 is justified.

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%, so all three parameters (folder_name, parent_folder_id, user_google_email) are already documented. The tool description does not add any parameter-level detail beyond what the schema provides. Per the baseline for high schema coverage, a score of 3 is appropriate.

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 the tool's function: 'Creates a new folder in Google Drive.' The verb 'Creates' and resource 'folder' distinguish it from sibling tools like create_drive_file or create_doc. The added detail about supporting shared drives further specifies its scope.

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?

No guidance is given on when to use this tool versus alternatives. The description does not mention any exclusions or alternative tools for creating files or documents. The only hint is 'supporting creation within shared drives,' but this does not constitute explicit usage direction.

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