mailu_delete_domain

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

The description explicitly says the operation is 'Irreversible' and that it deletes associated mailboxes and aliases. This provides critical behavioral context beyond the tool name, compensating for the lack of annotations.

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 a single sentence that is concise and front-loaded with the action. Every word contributes value, and there is no superfluous text.

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, the description covers the key aspects: what is deleted and its irreversibility. However, it does not mention the expected return value or error scenarios, which would be helpful for a more complete understanding.

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 only parameter 'domain' is described in the schema as 'Nom de domaine'. The description does not add any additional meaning or usage details beyond what the schema already provides. With 100% schema coverage, baseline score of 3 is appropriate.

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 verb 'Supprime' (delete) and resource 'domaine', with additional context that it also deletes associated mailboxes/aliases. It distinguishes itself from sibling tools like mailu_create_domain or mailu_update_domain.

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 that this tool is for deleting a domain, but it does not explicitly state when to use it versus other delete tools (e.g., delete_relay). No prerequisites or exclusions are mentioned.

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