drive_create_folder

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

Annotations already communicate that this is not read-only and not destructive. The description adds the useful behavioral detail that the folder may be created inside another folder, but it does not disclose side effects, permission requirements, or what happens when parentId is omitted.

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 short sentence with no filler. It leads with the core action and appends the only important qualifier, making it easy to scan and immediately actionable.

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 create operation this is mostly adequate, and annotations cover the read-only/destructive profile. However, there is no output schema and the description does not state what the tool returns (e.g., the created folder's ID), which an agent may need to chain subsequent calls.

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 compensate. It clarifies that parentId is optional and represents a container folder, while name is clearly the folder's name. However, it does not specify the expected value format for parentId or confirm behavior when parentId is absent.

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 states a specific verb ('create') and resource ('folder'), and the optional placement inside another folder adds scoping that distinguishes it from related sibling tools. The tool name reinforces the resource, and no other sibling creates Drive folders, so confusion is unlikely.

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 clearly communicates the primary use case: creating a folder, with an optional parent folder. It does not explicitly name alternatives or when-not-to-use conditions, but no sibling tool serves the same purpose, so the context is sufficiently clear without exclusions.

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