create_folder

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

No annotations are provided, so the description carries the full burden. It discloses the auto-encoding behavior for names with Cyrillic to IMAP modified UTF-7, which is useful. However, it does not mention error conditions (e.g., duplicate folder name), permission requirements, or side effects.

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 two sentences long and contains no filler. Every word adds value: the purpose statement and the encoding clarification.

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?

Given the tool has only one parameter, no output schema, and no annotations, the description is reasonably complete. It explains the core action and the key behavioral detail (name encoding). It could mention whether folder creation is idempotent or what happens if the folder already exists, but for a simple creation tool, it is sufficient.

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%, meaning the description must compensate. It adds meaningful context: the name parameter supports human-readable strings including Cyrillic, and will be auto-encoded. This goes beyond the bare schema type definition and helps the agent understand valid inputs.

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 'Create a new mail folder' with a specific verb and resource. It also adds detail about name encoding (Cyrillic, IMAP modified UTF-7), and this action is distinct from sibling tools like rename_folder or delete_folder.

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?

No guidance on when to use this tool versus alternatives (e.g., rename_folder, bulk_move). There is no mention of prerequisites, conditions for creating folders, or when not to use it.

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