stalwart_delete_account

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

With no annotations provided, the description carries the full burden of disclosure. It explicitly flags the operation as 'Destructive' and mandates confirm=True, providing essential risk information for an AI agent. It could add more detail about irreversibility or cascading effects, but the core safety cue is present.

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 concise and front-loaded, stating the action and warning in two short sentences, followed by a compact parameter list. Every sentence contributes value.

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 tool with a defined output schema, the description covers the essential aspects: what it does, the danger, the mandatory confirmation, and parameter semantics. Nothing critical is missing.

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 input schema has zero description coverage, but the description compensates by explaining both parameters: account_id is sourced from stalwart_list_accounts, and confirm must be True to proceed. This gives the agent the necessary context to correctly set arguments.

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 action ('Delete a mail account') with a specific verb and resource. It distinguishes from sibling delete tools by specifying 'account' as the target, making the purpose 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?

It provides clear operational guidance by warning that the operation is destructive and requires confirm=True. However, it does not explicitly discuss when not to use it or mention alternatives, but the context of deleting a mail account is unambiguous.

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