delete_episodes_subtitles

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

Annotations already indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=true, and the description merely restates the delete behavior without adding consequences, permissions, or side effects. It also fails to explain what happens to the file or system state when subtitles are deleted.

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 tight and well-structured: a clear one-line purpose, the HTTP endpoint, and a compact argument list. No filler is present, though the endpoint line is arguably redundant with the tool name.

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?

The description covers all required parameters and the destructive nature of the operation, and an output schema exists for return values. However, it lacks usage guidance, clarification of forced/HI semantics, and any behavioral caveats, making it adequate but not fully complete for a six-parameter delete operation.

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 Args section must carry the documentation burden. It does provide meaningful hints for all six parameters, such as 'Language code2', 'Forced true/false as string', 'HI true/false as string', and 'Path of the subtitles file', though some entries like 'Series ID' add limited detail.

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 opens with a specific verb and resource: 'Delete an episode subtitles,' and reinforces it with the DELETE endpoint. This clearly separates it from sibling tools like create_episodes_subtitles, patch_episodes_subtitles, and delete_movies_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?

The description gives no explicit guidance on when to use this tool versus alternatives. It does not mention that creation, patching, or movie-subtitle deletion belong to other tools, leaving the agent to infer usage solely from the verb 'delete'.

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