sonarr_delete_importlist

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

The annotations already declare `destructiveHint: true` and `readOnlyHint: false`; the description merely restates this with 'DESTRUCTIVE: this deletes data.' It adds no additional behavioral context, such as irreversibility, cascading effects, or required permissions, beyond what the annotations already provide.

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 very short and front-loaded, with the action stated first. The second sentence is somewhat redundant given the annotations, but it is not verbose and the overall structure is clear and scannable.

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 simple one-parameter destructive delete, the description plus annotations and output schema cover the basic invocation. However, it misses important contextual details like singular vs. bulk operation, irreversibility, and the alternative bulk delete tool, making it slightly under-specified in the broader API context.

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?

With 0% schema description coverage and only one integer parameter `id`, the description fails to explain what the `id` refers to or how to find it. While the tool name implies the ID is for an import list, the description adds no meaning beyond the schema's bare type declaration.

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 ('import lists'), which is specific and understandable. However, it does not differentiate this single-item delete tool from its sibling `sonarr_delete_importlist_bulk`, which also deletes import 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?

There is no guidance about when to use this tool versus `sonarr_delete_importlist_bulk` or other import list operations. The description omits any mention of prerequisites, such as how to obtain the import list ID, and provides no exclusion criteria.

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