create_folder

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly identifies the mutation (creating a folder), scopes it to Google Drive, and documents the return value (created folder with id and link). It does not discuss permissions or failure modes, but for this simple create operation the stated behavior is sufficiently transparent.

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 compact, front-loaded with a one-sentence purpose, and uses an Args/Returns structure with no filler. Every sentence adds information needed to call the tool correctly.

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 two-parameter folder-creation tool with an output schema, the description fully covers the input semantics, optional parent behavior, and return shape. There are no missing details an agent needs to invoke it correctly.

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 does by naming each parameter and explaining the parent_id behavior with 'None for root.' The name parameter's explanation is minimal, but the parent_id guidance adds a semantic distinction beyond the schema's type and default.

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 line states a specific action ('Create') and resource ('new folder in Google Drive'), and folder creation is distinct from sibling file operations like upload_file, search_files, and share_file. The purpose is unmistakable and correctly matches the tool name.

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 clear context: use this tool when the goal is to create a folder in Google Drive, not to upload or manipulate files. It does not explicitly name alternatives or exclusions, but for a folder-creation tool the intended trigger is obvious and no exclusion is needed.

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