Create Mailbox

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

Annotations already declare readOnlyHint=false (write), destructiveHint=false, idempotentHint=true. The description adds no additional behavioral context (e.g., permission requirements, side effects, rate limits) beyond what annotations provide.

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?

Two concise sentences with no extraneous information. The first sentence states the purpose, the second provides a key usage step.

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?

Despite having an output schema, the description omits important context about optional parameters (e.g., when to use password vs generate_password) and does not fully leverage the six parameters. Given the large set of sibling tools, more detail would increase completeness.

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 33%. The description does not explain any parameter semantics (e.g., the address pattern, the interaction between password and generate_password). It only mentions domain_id indirectly via the prerequisite.

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 action ('Create a mailbox on an existing domain') and distinguishes from siblings by specifying a prerequisite ('Use shipmail_list_domains first to find the domain ID'). It uses a specific verb+resource structure.

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?

The description provides a clear usage context (create mailbox on existing domain) and a direct prerequisite (list domains to get domain ID). However, it does not explicitly mention when not to use or alternatives among the many mailbox-related siblings.

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