create-mailbox

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

No annotations provided, so description carries burden. It discloses that it creates a real folder and returns confirmation, and includes a safety note. However, it does not detail behavior on duplicate names, permission requirements, or error handling.

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?

Description is relatively concise at 4 sentences. It is front-loaded with 'Use when' and structured with clear sections, though some redundancy exists (e.g., repeating 'use' phrasing).

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 and presence of an output schema (return confirmation mentioned), description covers essential aspects but lacks depth on parameter details and potential side effects.

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 has 2 parameters: name (no description) and account (described). Description mentions 'target account' but does not elaborate on the name parameter or provide additional format/validation info 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?

Description explicitly states the purpose: 'creating a new mailbox/folder in an account.' It uses a specific verb and resource, and distinguishes from sibling tools like rename-mailbox and delete-mailbox.

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?

Clearly states when to use ('creating a new mailbox/folder') and when not to use ('renaming an existing one ... or deleting one'). Provides alternatives (rename-mailbox, delete-mailbox) and suggests list-mailboxes to check existing ones.

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