stalwart_delete_mailing_list

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 explicitly states 'Destructive' and requires `confirm=True`, warning the agent of the irreversible nature and the safety check. It could add more detail about cascading effects, but the core danger is disclosed.

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 only two sentences plus an args list. It front-loads the destructive nature and condenses essential usage into a compact format.

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 destructive operation with an output schema present, the description is largely complete. It covers what the tool does, the source of the parameter, and the confirmation requirement. Missing details like permission requirements or effects on members are minor gaps.

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 description explains both parameters beyond the schema: `list_id` provenance and `confirm` semantics ('must be True to proceed'). Given schema descriptions are absent (0% coverage), this added guidance is valuable.

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 'Delete a mailing list,' a specific verb and resource. This clearly distinguishes it from sibling tools like stalwart_create_mailing_list and stalwart_delete_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?

It provides context by instructing that `list_id` should come from `stalwart_list_objects(obj_type='mailing_list')`, giving a clear precondition. It does not explicitly mention alternative tools or exclusions, but the targeted deletion context is clear.

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