create_email_account

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

Without annotations, the description adds value by flagging the mutation, requiring confirmation, and setting a limit. However, it doesn't cover OAuth configuration (only mentions IMAP/SMTP), which is present in the schema.

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 sentences: first defines purpose, second adds constraints and behavior. Very concise and front-loaded with critical 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 19 parameters and no output schema or annotations, the description covers purpose, limit, and mutation traits. Missing return value details and OAuth mention, but the schema fills gaps. Decent completeness for a creation tool.

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?

With 100% schema coverage, the baseline is 3. The description adds a business constraint (max 10 accounts) and a confirmation flag, exceeding schema documentation.

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 tool creates a new email account with IMAP/SMTP configuration, distinguishing it from other email-related siblings like update_email_account or delete_email_account.

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 a usage limit (max 10 per store) and a confirmation requirement (confirm=true), which guides the agent on when to use. Lacks explicit alternatives but clearly defines conditions for execution.

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