create-mail-folder

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

The description adds context beyond annotations (destructiveHint=true) by specifying the folder location (root) and the isHidden property behavior. It does not discuss error states or full behavioral traits but covers key aspects.

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 plus a tip—tight and front-loaded with the action. Every sentence adds value without redundancy.

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 complex input schema (nested objects) and no output schema, the description adequately explains the tool's purpose and key creation behavior. It does not cover all edge cases but is sufficient for the main use case.

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 description adds meaning beyond the schema by noting that isHidden can be set on creation, which helps with the body parameter. Schema coverage is 67%, but the description compensates with this specific guidance.

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 mail folder in the root folder of the user's mailbox. It also mentions the ability to set isHidden for hidden folders, and the tool name is self-explanatory. It contrasts with create-mail-child-folder, making the purpose 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?

The description explicitly says 'Use this API to create a new mail folder in the root folder' and provides a tip differentiating from create-mail-child-folder and referencing list-mail-folders for existing folder IDs. This gives clear when-to-use and alternative guidance.

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