create-mail-child-folder

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

Annotations already indicate destructiveHint: true, so the description's additional context about isHidden property being set only at creation adds value. However, it does not disclose other behavioral aspects such as required permissions, reversibility, or rate limits, which would be beneficial.

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 very concise, with one main sentence and a helpful tip. No wasted words, and the tip is front-loaded for quick understanding.

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?

The description covers key aspects like hiding and parent folder look-up, but lacks details about the output (the created folder is likely returned, but not stated) and error handling. Given the complexity of nested objects and no output schema, more completeness would be helpful.

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 covers 75% of parameters with descriptions, so the description's additional note on isHidden property provides some extra meaning. Baseline is appropriate as the schema does most of the documentation work.

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 tool creates a new child mailFolder (subfolder) within an existing folder. It uses specific verbs and resource names, and distinguishes from top-level folder creation by referencing parent folder ID and sibling tools list-mail-folders.

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 provides a tip to use list-mail-folders or list-mail-child-folders to find the parent folder ID, offering clear guidance on prerequisite steps. It also notes the isHidden property must be set at creation. However, it does not explicitly state when not to use this tool (e.g., for top-level folders, use create-mail-folder instead).

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