stalwart_create_account

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

With no annotations, the description must carry the behavioral burden. It adds useful context: name creates alice@domain.com, password is the initial password, and locale/time_zone have defaults. However, it does not disclose permissions, duplicate-name behavior, whether a null password is allowed, or what the response contains.

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 front-loaded with a one-sentence purpose and followed by a concise Args list. Every parameter line adds distinct value and there is no filler or repetition.

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?

The description covers all input parameters, includes defaults, and references the needed domain source. With an output schema present, return values need not be detailed. Minor gaps remain around null password behavior and duplicate account handling, but these do not seriously undermine usability.

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 0%, but the description fully compensates by explaining all six parameters. It adds a local-part example, source for domain_id, optional status for description, and defaults for locale and time_zone, going well beyond the bare 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?

The description opens with 'Create a new mail account (user)', a specific verb and resource. It also clarifies that 'name' is the local part, distinguishing it from related account tools like list, get, delete, or set password.

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 implies this is the tool for creating accounts and explicitly directs users to stalwart_list_domains for domain_id. It does not state when not to use it or contrast with stalwart_set_account_password, but the context is clear and actionable.

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