create-mail-child-folder

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which align with creation. The description adds nuance about setting isHidden on creation but does not disclose other side effects or error conditions. With high annotation coverage, a score of 3 is appropriate.

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 extremely concise with two sentences and a tip, front-loading the key action. Every sentence adds value, with no wasted words.

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 tool's simplicity, annotations, and sibling context, the description covers creation of a child folder, the hidden property nuance, and how to find the parent. It could mention that the tool returns the created folder object, but since there is no output schema, this is a minor gap.

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 75%, so the schema already documents most parameters. The description adds value by highlighting the isHidden property but does not elaborate on other parameters like mailFolderId or body structure. Baseline 3 is reasonable.

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 child mailFolder (subfolder) within an existing folder, using the verb 'create' and specifying the resource. It distinguishes from create-mail-folder by emphasizing 'child' and provides context about using list-mail-folders to find the parent ID.

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 gives a tip to use list-mail-folders or list-mail-child-folders to find the parent folder ID, providing clear context. However, it does not explicitly state when not to use this tool or mention prerequisites like ensuring the parent folder exists.

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