Create a Drive folder

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

Annotations already indicate mutation (readOnlyHint=false). Description adds valuable behavioral context: return value (folder id + webViewLink) and the distinction between the returned ID and the NAME used by save_to_drive. While it doesn't cover error handling or permissions, it goes beyond annotations without contradiction.

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?

Three sentences, each adding distinct value: purpose, return value, and usage warnings. No fluff; information is front-loaded and logically ordered. The critical save_to_drive clarification is placed at the end, which is acceptable.

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 tool with full schema coverage and relevant annotations, the description covers purpose, return value, usage pattern, and potential confusion with sibling tools. Nothing an agent needs to call it correctly is missing.

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 already documents both parameters (100% coverage). Description adds meaning by explaining parentId's role ('parent folder id for a nested folder, default: Drive root') and clarifies the id/name distinction for name usage. This enriches the schema's baseline descriptions.

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?

Description states a specific verb ('Create') and resource ('folder in the user’s Google Drive') with optional nesting under parentId, clearly distinguishing it from siblings like save_to_drive and update_drive_file. The purpose is immediately clear without ambiguity.

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?

Provides explicit when-to-use guidance: 'Use that ID as update_drive_file’s moveToFolderId or as parentId for a nested folder.' Also warns about save_to_drive's folder being a NAME not an id, and advises passing the NAME there or omitting it. This fully routes the agent to correct alternatives.

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