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 of behavioral disclosure. It only states that a folder or mailbox is created; it does not mention side effects, permissions, duplicate-name behavior, reversibility, or what the API returns on success. For a mutation tool, this is a significant transparency gap.

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 efficient sentence with the action front-loaded. It avoids unnecessary padding, though the 'folder or mailbox' qualifier could be more precise without making the description longer.

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?

With only one parameter, the tool is simple, but the description leaves important context unexplained: the difference between a folder and a mailbox, behavior on duplicate names, and expected return values. There is no output schema and no annotations to fill these gaps, so the description alone is not fully 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 description coverage is 100%, with the 'name' parameter already documented as 'Name of the new folder or mailbox to create.' The tool description adds no meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 the action (create) and the resource (folder or mailbox) in the one.com mail account. It is distinct from sibling tools like rename_folder and delete_folder, though the 'folder or mailbox' wording introduces some ambiguity about the exact resource type.

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 intended use is implied by the verb 'Create' and the resource type, but there are no explicit conditions, prerequisites, or exclusions. Since no other sibling tool creates folders or mailboxes, the usage context is reasonably clear, but the description does not guide the agent on when to choose a folder versus a mailbox.

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