drive_create_folder

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

With no annotations, the description must disclose behavioral traits on its own. It only states the mutation (creation) without mentioning potential side effects, such as whether duplicate folder names are allowed, what happens when the parentId is invalid, or what the function returns. This lack of detail reduces transparency for a mutation tool.

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 states the essential purpose without any fluff or unnecessary detail. Every word earns its place, making it highly efficient.

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?

The tool is relatively simple, and the description covers the core action. However, it lacks information about the return value (e.g., the new folder's ID) and edge-case behavior (e.g., duplicate names, invalid parent ID). Since there is no output schema and no annotations, the description should provide more context to be 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?

The input schema provides 100% coverage of both parameters ('name' with a description and 'parentId' with a description). The tool description adds no additional parameter semantics, so the baseline score of 3 is appropriate since the schema already documents the parameters.

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 'Create a new folder in Google Drive' clearly states the action (create) and the resource (folder in Google Drive). It distinguishes this tool from siblings like drive_list_files, drive_upload_text_file, and drive_download_file, which perform different operations.

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 gives no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, like whether a parent folder is needed, nor does it suggest other tools for file operations. Usage is only implied by the action 'create a new folder'.

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