delete_movies_blacklist

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

Annotations already indicate destructiveHint=true and idempotentHint=true, so the description does not need to restate deletion. It adds some useful behavioral context by noting that 'all' empties the movies subtitles blacklist, but it does not disclose side effects or whether a specific deletion requires both provider and subs_id.

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-loads the action and endpoint, followed by a compact argument list. The grammar is slightly awkward ('a movies subtitles'), but there is no redundant filler and every line serves a purpose.

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 output schema exists and annotations cover safety and idempotency, the description only needs to explain the operation and parameters. It covers both, but it leaves the key decision implicit: whether to use 'all' to clear everything or provider+subs_id to delete one entry, and which combinations are valid.

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 description coverage is 0%, so the description must compensate for the bare schema. It gives a one-line meaning for each argument, which adds value beyond the schema, but the semantics of 'all' is terse and the relationship between all, provider, and subs_id is left implicit.

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 states a clear action ('Delete'), a resource ('movies subtitles'), and the target context ('blacklist'), and the endpoint line reinforces it. It is distinct enough from sibling tools like delete_movies_subtitles and delete_episodes_blacklist, though it does not explicitly call out the distinction.

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 description provides no guidance on when to use this tool versus sibling alternatives such as delete_movies_subtitles or delete_episodes_blacklist. The purpose is implied but there are no conditions, exclusions, or preference signals to help an agent choose correctly.

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