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

Beyond the destructive annotation, the description states that deletion is immediate, that CSV and archive files are removed from the workspace, and that the operation is refused when a batch or Flow run is active. It also notes that the operation is free, which is useful pricing context.

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 front-loaded with the action and side effects, then gives the refusal condition and pricing note. Every sentence earns its place 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 tool with annotations and no output schema, the description covers the key behavior: immediate deletion, file removal, and the active-run refusal. Minor gaps remain, such as what happens when list_id is not found or whether related artifacts like pages are affected, but these do not block correct invocation.

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% and list_id is already documented as the value returned by create_list. The description adds no further parameter semantics, which is acceptable because the schema carries that burden.

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 uses a specific verb and resource: delete one Hosted List, including removal of its stored CSV and archive files. It is clear what is being deleted, but it does not explicitly distinguish this tool from the bulk sibling purge_lists.

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 single-list scope is implied, and the refusal condition for active batch or Flow runs is given. However, there is no explicit when-to-use guidance versus alternatives such as purge_lists, so the agent must infer the routing.

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