create_episodes_blacklist

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds no extra behavioral context beyond the implicit write action; it doesn't explain side effects, reversibility, or the impact of blacklisting (e.g., preventing future subtitle downloads). It fails to disclose any details that would inform an agent how the system changes state.

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 concise, includes the endpoint and a parameter list with brief labels, and front-loads the purpose. It has minor grammatical imperfection but no redundancy or clutter, making it efficient to parse.

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 tool has 6 required parameters, no enums, and an output schema, the description covers the basics but lacks contextual details. It doesn't explain the business logic of blacklisting, when it's needed, or what the response indicates. The absence of usage guidance and behavioral depth makes it minimally adequate for an agent to call, but not fully self-sufficient.

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 description provides slightly more readable labels than the schema titles (e.g., 'Series ID' vs 'Seriesid', 'Subtitles file path' vs 'Subtitles Path') and lists all parameters. However, it doesn't explain the meaning of each parameter in the context of blacklisting (e.g., what 'provider' refers to, how 'language' is used) or any relationships between them, leaving gaps that the schema also fails to fill (0% coverage).

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 specific action ('Add an episodes subtitles to blacklist') with a clear resource and verb, and the tool name reinforces the blacklist concept. It distinguishes from siblings like delete_episodes_blacklist and create_episodes_subtitles, though the phrasing is slightly awkward ('an episodes subtitles').

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 like delete_episodes_blacklist or create_episodes_subtitles. No mention of prerequisites, conditions, or scenarios where blacklisting is appropriate, leaving the agent to infer usage solely from the name.

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