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 behavioral burden. It only states that the action is a POST to /api/folders and provides example names; it does not disclose duplicate-folder behavior, permissions, side effects, or the response format.

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 front-loaded sentence that clearly covers the operation, endpoint, and representative naming examples. There is no repetition or filler.

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 one-parameter creation tool, the description is mostly sufficient and includes a helpful endpoint and naming example. It is not fully complete because it omits expected response behavior, duplicate handling, and whether any authentication or existing-folder checks are required.

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 schema already documents the single 'name' parameter, so the baseline is 3. The description adds useful meaning with examples: 'Work' shows a simple folder name, while 'mail/aze-walid' suggests slash-separated hierarchical folder paths are accepted.

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 phrase 'Create a new mail dossier/folder (POST /api/folders)' clearly states the action and resource, and includes the exact endpoint. It is understandable on its own, but it does not explicitly differentiate this from the sibling tool 'create_folder_for_email'.

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?

There is no guidance about when to use this tool instead of 'list_folders', 'create_folder_for_email', or 'move_email_to_folder'. Prerequisites such as authentication or checking for an existing folder are also not mentioned, so an agent gets little decision support.

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