create-mail-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 useful context: it creates a folder in the root, and the isHidden property must be set at creation. No contradictions, but does not elaborate on further side effects.

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?

Extremely concise: two sentences and a tip, no fluff. Front-loaded with the main action. Every sentence serves a purpose.

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 the core purpose, usage guidelines, and a key parameter detail. It lacks information about the return value, but given no output schema and the presence of sibling tools for context, it is adequately complete for a creation tool.

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 67% (moderate). The description highlights the isHidden property as a behavioral requirement, which adds value beyond the schema. However, most parameter details are left to the 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 verb 'create' and resource 'mail folder', specifying it's at the root. It distinguishes from sibling tool 'create-mail-child-folder' by noting this creates top-level 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?

Explicitly provides when to use this tool (root folder) vs alternatives: mentions 'create-mail-child-folder' for subfolders and 'list-mail-folders' to find folder IDs. Also gives a specific tip about setting isHidden on creation.

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