delete_import_list

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

There are no annotations, so the description carries the full behavioral burden. It only repeats the delete action and does not disclose irreversibility, side effects on related data, error behavior, or any confirmation/return semantics.

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 short sentence with no filler, which is appropriately concise for such a simple operation. The grammatical error 'a import list' is a minor quality issue, but the structure is otherwise clean and front-loaded.

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 destructive tool with no annotations and no output schema, the description is too thin. It does not tell the agent how to obtain the required id, that the operation is irreversible, or what to expect after deletion.

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 fully documents the single parameter id with the description 'import list id', so schema coverage is 100%. The description adds no additional parameter meaning, but the baseline of 3 applies because the schema already carries the necessary detail.

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 action ('Delete') and the resource ('a import list'), which is a specific, identifiable object. It is also distinct from the sibling delete_import_list_exclusion because it names the import list itself rather than an exclusion.

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?

No guidance is provided about when to use this tool versus alternatives, such as delete_import_list_exclusion or update_import_list. There is no mention of prerequisites like obtaining the id via list_import_lists, and no exclusionary guidance is given.

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