seerr_delete_watchlist

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

The description merely restates the destructiveHint annotation with 'DESTRUCTIVE: this deletes data,' adding no new behavioral context such as irreversibility, permissions required, or side effects. It provides no additional transparency beyond the annotations.

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 extremely concise, with the destructive alert front-loaded. However, the phrase 'DESTRUCTIVE: this deletes data' is redundant with the annotations, making it not fully earn its place.

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?

Given the presence of an output schema, the return value is covered, but the tool still lacks parameter explanations and usage context. A simple tool with two required parameters still needs more guidance for 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?

With 0% schema coverage and no parameter descriptions, the description fails to explain 'tmdb_id' or 'media_type'. The names are slightly suggestive but not sufficiently defined, and the description adds no semantic meaning for the parameters.

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 ('watchlist item'), making the tool's purpose unmistakable. It distinguishes itself from sibling tools like seerr_create_watchlist and seerr_get_user_watchlist by the explicit 'Delete' verb.

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 alternatives, no exclusions, or prerequisite conditions. The description only states the action without any contextual direction for the agent.

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