delete_movies_subtitles

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description merely repeats the delete semantics without adding context about irreversibility, what is removed on disk versus database, or failure behavior. It does not contradict the annotations, but adds no behavioral value beyond them.

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 compact and scannable, with the action front-loaded and an organized Args block. The endpoint line is somewhat redundant with the tool name, but overall there is no filler or wasted prose.

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 operation with five required parameters, the description leaves important gaps: accepted value formats for forced/hi, what exactly gets deleted, and when to prefer create/patch variants. The output schema exists, so return values need not be described, but behavioral and parameter context is still thin.

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 description coverage, the Args list is essential and does add some meaning: radarrid=Movie ID, language=Language code2, path=Path of the subtitles file. However, forced and hi only restate that they are true/false strings without explaining accepted values or their meaning, and 'Language code2' is ambiguous about exact format.

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 opening sentence 'Delete a movie subtitles' states a specific verb and resource, and the DELETE endpoint reinforces the action. It is distinct from siblings like create_movies_subtitles or delete_episodes_subtitles, though it never explicitly calls out those differences.

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 when-to-use or alternative routing is provided. The description only states the delete action and parameters, leaving the agent to infer when to choose this over patch_movies_subtitles or delete_episodes_subtitles from the tool name alone.

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