Create mailbox

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, covering the safety and idempotency profile. The description adds useful context about nested folder syntax but does not describe what happens if the folder already exists, whether parent folders are auto-created, or any permission requirements.

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?

Three short sentences, front-loaded with the core action, followed by syntax guidance and a helpful cross-reference. Every sentence earns its place with no redundancy.

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?

For a simple creation tool with full schema coverage and relevant annotations, the description covers purpose, path syntax, and a useful sibling reference. A minor gap remains around conflict handling and whether parent directories are created automatically, but annotations mitigate the idempotency concern.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by explicitly specifying the '/' separator for nested folders and giving an example ('Work/Projects'), which clarifies how the 'path' parameter can be structured.

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?

States a specific verb ('Create') and resource ('mailbox (folder)'), and immediately clarifies that mailbox means folder. It distinguishes itself from siblings like list_mailboxes and delete_mailbox by explicitly naming the read-only alternative.

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?

Points to list_mailboxes for checking existing folders, which is a clear contextual alternative. However, it does not explicitly state when not to use this tool or outline prerequisites (e.g., required permissions).

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