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

Goes well beyond destructiveHint=true by disclosing exactly what is destroyed (the list and its memberships) and, more importantly, what is NOT (the contacts). It also reveals a non-obvious side effect: automations anchored to contact.list_added on this list stop receiving entries.

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?

Three short sentences, front-loaded with the core action, then scope clarification, then the side-effect warning. Every sentence carries distinct information with no filler.

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 delete with no output schema, the description covers impact on memberships, contacts, and automations, which is the information an agent most needs. It stops short of stating reversibility, required permissions, or whether the list must be empty.

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 description coverage is 0%, so the schema itself carries no meaning for listId, and the description adds nothing about it. However, a single required uuid named listId is effectively self-describing, so the gap is minor rather than disqualifying.

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 (deletes a list and its memberships) and immediately disambiguates scope by clarifying that contacts are preserved, which separates it from delete_contact and remove_contacts_from_list. An agent can distinguish it from all delete_* siblings without opening a 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?

Gives a concrete pre-flight condition: check list_automations before deleting if automations trigger on contact.list_added. The 'you remove the list, not the people' line implicitly routes to remove_contacts_from_list for the narrower operation, but no alternative is named explicitly and no prerequisite (e.g., confirmation, ownership) is stated.

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