Create Folder

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

Annotations already indicate non-read-only and non-destructive. Description adds naming convention detail but does not mention side effects, permissions, or error conditions (e.g., duplicate names). No contradiction with annotations.

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?

Two sentences, no fluff, directly to the point. Slightly could be improved by structuring usage hints more explicitly, but overall concise.

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?

Covers basic naming and prerequisite, but lacks details on error handling (e.g., duplicate folder), permissions, or return values. Output schema may compensate, but description alone is minimally 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?

Schema coverage is 100%, and description adds value by explaining the folderName format (Folders/Name vs Labels/Name), which is more specific than the schema description ('Folder path to create').

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 it creates a new email folder or label, with specific naming conventions (Folders/ vs Labels/). However, it does not explicitly differentiate from sibling tools like move_to_folder or rename_folder, though the creation purpose is distinct.

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 context on when to use (before move_to_label) and naming format, but lacks alternative recommendations or when not to use. No explicit exclusions despite many sibling tools.

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