create_mailbox

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

With no annotations, the description must disclose behavior. It explains nesting creates intermediate segments if needed, but does not mention error handling for duplicate names, permissions, or scope of the operation.

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?

Concise with clear structure: main purpose, nesting explanation, Args list, Returns. Minor redundancy in the nesting examples but overall well-organized and front-loaded.

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?

Covers basic usage and returns confirmation path, but lacks details on error states, permission requirements, or behavior when mailbox name conflicts. Output schema is present but minimal; description could be more complete.

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 0%, but the description explains each parameter: account (account name), name (can include slashes for nesting), parent_mailbox (optional existing folder). Adds significant meaning beyond the bare 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?

Clearly states 'Create a new mailbox (folder)' with specific verb and resource. Explains nested path creation via parent_mailbox or slash-separated name, differentiating it from sibling tools that list or manage emails.

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?

Provides two alternative usage patterns for nesting (parent_mailbox vs. slash-separated name). Lacks explicit conditions for when not to use (e.g., if mailbox already exists) or comparison with sibling tools, but the given guidance is clear.

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