mail_domain_add

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

No annotations are provided, so the description carries full disclosure burden. It reveals only that the tool creates something, with no information about side effects, duplicate domain handling, default behavior of 'active', dependencies on existing resources, or response expectations.

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 five-word description is front-loaded with the verb and contains no filler. However, this brevity results from omitting usage and behavioral content rather than from dense compression, so it borders on under-specification.

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 creation tool with no annotations, no output schema, and a loosely-typed nested params object, the description is inadequate. It does not explain the semantics of the params keys, what a successful call returns, or how it fits with the adjacent mail_* creation tools, leaving the agent to infer too much from the schema alone.

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 of 3 applies. Both client_id and params have descriptions, with params enumerating the keys (server_id, domain, active), but the schema only gives key names with no type or semantic detail for 'active' or 'server_id', and the tool description adds no parameter explanation beyond the 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?

States a specific verb and resource ('Create a new mail domain') that accurately describes the operation. The verb distinguishes it from sibling mail_domain_list, mail_domain_get, and mail_domain_delete, though these are not explicitly named.

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?

No guidance on when to use this tool versus alternatives such as web_domain_add, dns_zone_add, or mail_catchall_add. No prerequisites (existing client, server) or exclusion conditions are stated.

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