radarr_delete_importlist

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

The annotation already declares destructiveHint=true, and the description merely repeats 'DESTRUCTIVE: this deletes data' without adding new context. It does not explain potential cascading effects (e.g., associated import list movies), irreversibility, or error behavior, so it adds no value beyond the structured annotation.

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 short and front-loaded, but the second sentence ('DESTRUCTIVE: this deletes data.') is redundant with the annotations and adds no value. It is concise but not optimally structured since it wastes a sentence repeating existing metadata.

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 delete-by-ID tool, annotations cover the destructive nature and an output schema exists, so return values need no explanation. However, the description lacks any usage context, such as whether the tool deletes a single import list, error handling for non-existent IDs, or guidance on choosing between this and the bulk delete sibling.

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 input schema has one required 'id' integer parameter, and schema description coverage is 0%. The description does not mention the parameter or explain what the ID refers to. While the ID is self-explanatory given the tool name, the description fails to compensate for the lack of schema documentation.

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 resource (import lists), making the core purpose unambiguous. However, it does not distinguish this tool from the sibling radarr_bulk_delete_importlist, and the plural 'import lists' could imply deleting all at once rather than a single instance by ID.

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 radarr_bulk_delete_importlist or other delete tools. The description does not specify prerequisites, recommended scenarios, or exclusions, leaving the agent to infer usage solely from the tool name.

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