mailchimp_lists_delete

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

With no annotations, the description must disclose behavioral traits. It discloses that the deletion is permanent and affects all members, which is critical context. However, it omits other potential side effects (e.g., deletion of associated segments, automation triggers) and any permission requirements, leaving the agent with partial transparency.

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, compact sentence that directly states the action and its primary consequence. Every word is necessary, and the key information is front-loaded ('Permanently delete').

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 minimal delete tool, the description covers the core functionality but lacks context about return values, restrictions, or cascading consequences beyond members. It does not explain what happens to related resources, so the agent may not fully understand the tool's impact. The absence of an output schema and annotations increases the burden, but the simplicity of the tool keeps it at a passable level.

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 provides 100% coverage of the single parameter, 'list_id' with the description 'List ID to delete', which is sufficient. The tool description adds no additional parameter semantics beyond the schema, so a 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 'Permanently delete a list and all its members' clearly states the action (permanently delete), the resource (a list), and the scope (including members). This distinguishes it from sibling tools like mailchimp_lists_delete_segment and mailchimp_members_delete, which target different resources.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention when not to use it (e.g., if only removing a segment) or any prerequisites. The description simply asserts the action, leaving usage decisions to the agent without additional context.

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