create-mail-child-folder

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

Annotations already indicate destructiveHint=true and readOnlyHint=false; the description adds that isHidden must be set at creation, which is a useful constraint. However, it does not disclose other behaviors like auth needs, rate limits, or what happens to existing folders.

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?

Two sentences plus a tip. Front-loaded with the main purpose. Every sentence adds value, no 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?

Despite schema richness, the description does not explain how to construct the required 'body' parameter (e.g., at least displayName is necessary) or describe the return value. For a creation tool with no output schema, this gap hinders correct invocation.

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 coverage is high (75%), so the schema already explains parameters. The description only mentions isHidden in context, adding minimal extra meaning. The tip indirectly references mailFolderId. No additional syntax or format details beyond schema.

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'), the resource ('child mailFolder'), and a specific nuance (hidden folders require setting isHidden on creation). It distinguishes from sibling tools like 'create-mail-folder' by specifying 'child' and provides a tip referencing related list tools.

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 to use this API to create a child mailFolder and advises using list-mail-folders or list-mail-child-folders to find the parent folder ID. It implicitly excludes top-level folder creation but does not state alternatives explicitly.

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