Delete Mailing List

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description earns credit by adding cascade semantics that annotations cannot express: the deletion is permanent and removes only list membership, not the subscriber records themselves. It does not say what happens if the id does not exist or whether dependent campaigns are affected.

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?

Two short sentences, zero filler, with the permanent-deletion warning and the cascade scope front-loaded. Nothing restates the tool name verbatim without adding information.

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 one-parameter destructive tool with strong annotations and no output schema, the description covers permanence and cascade effects, which is most of what an agent needs. Missing only failure behavior on unknown ids and any confirmation/precondition requirements.

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 coverage is 100% with a single documented list_id, so the schema does the heavy lifting. The description adds only the notion that the id refers to a mailing list, not a subscriber or campaign, which is a minor semantic gain over "Numeric id."

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 ("Permanently deletes a mailing list by id") with an explicit key, and the resource noun (mailing list) is clearly distinct from the many subscriber/campaign/template siblings. An agent can identify this as the list-level delete without opening any schema.

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?

Usage is only implied: an agent infers this is for removing a list entirely rather than using listmonk_update_list. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., removing memberships instead), though the note that subscribers survive does hint at the alternative of managing membership.

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