create_mailbox

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

With no annotations, the description explains nesting behavior and return value. It does not mention failure modes or idempotency, but the core behavior is transparent.

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 concise: one sentence for purpose, then examples, then parameter list, then return. No unnecessary information.

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 output schema exists, the return description is adequate. The description covers parameters and usage well, but could mention error conditions or permissions.

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 0%, so the description fully explains all three parameters: account, name (with slash-path capability), and optional parent_mailbox. Examples clarify nesting.

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 the resource 'mailbox (folder)', with explicit examples of nested path creation. It distinguishes itself from sibling tools like 'list_mailboxes' by focusing on creation.

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 clear use cases and two methods for nesting but does not explicitly state when not to use (e.g., for listing mailboxes). However, the context of siblings makes it largely clear.

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