delete_episodes_blacklist

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's 'Delete' is consistent. The description adds the behavior of the 'all' parameter ('Empty episodes subtitles blacklist'), which is not in annotations, but it does not explain the effect of combining parameters or any side effects beyond deletion. No contradiction with 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 short, includes the endpoint, and front-loads the action. The args list is compact but not well structured; however, it is not verbose. It earns a 4 for efficiency, though the terse phrasing could be improved.

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, idempotent tool with three optional parameters and no schema descriptions, the description is insufficient. It does not clarify the exact semantics of 'all' versus specific provider/subs_id combinations, nor does it mention what response to expect. Although an output schema exists, the behavior is still ambiguous. More context is needed 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, the description must fully explain the parameters. It gives terse hints: 'all: Empty episodes subtitles blacklist', 'provider: Provider name', 'subs_id: Subtitles ID'. This is ambiguous: 'Empty' likely means 'clear all', but it doesn't clarify whether 'all' is a boolean or string, or how it interacts with provider/subs_id. The description adds minimal meaning beyond the schema, leaving the agent uncertain about required combinations.

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 verb and resource: 'Delete an episodes subtitles from blacklist.' This distinguishes it from sibling tools like delete_movies_blacklist and delete_episodes_subtitles by resource and action. The inclusion of the endpoint adds specificity, though it does not explicitly name alternatives.

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 given on when to use this tool versus siblings. There is no mention of scenarios where this is preferred over delete_episodes_subtitles or create_episodes_blacklist. The description only states what it does, not when to use it.

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