stalwart_delete_domain

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly labels the operation as destructive and mandates confirm=True, which informs the agent about safety-critical behavior. It also adds context that domain_id comes from stalwart_list_domains, aiding correct usage.

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 extremely concise, front-loading the key fact ('Delete a mail domain. Destructive — requires confirm=True') before listing parameters. Every sentence earns its place with no wasted words.

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 delete operation with 2 parameters and an output schema, the description adequately covers the purpose, destructive nature, confirmation requirement, and parameter provenance. It doesn't detail post-delete effects on dependent data, but that's beyond minimal completeness for this 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?

The schema has 0% description coverage, leaving all parameter semantics to the description. The description fully explains both parameters: domain_id (source from stalwart_list_domains) and confirm (must be True to proceed). This adds complete meaning beyond the raw 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 starts with 'Delete a mail domain', which uses a specific verb and resource, clearly distinguishing it from sibling tools like create_domain or delete_account. The scope is unambiguous.

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 explicitly warns 'Destructive — requires confirm=True', providing clear context that this tool is dangerous and needs explicit user confirmation. It doesn't mention alternatives or when-not-to-use, but the destructive flag serves as a strong usage guideline.

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