remove_subtitle

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

No annotations are provided, so the description carries the full behavioral burden for a destructive mutation. It discloses the bulk-removal behavior via the omitted subtitle_id, but says nothing about reversibility, required permissions, or the effect on in-flight playback, which is a significant gap for a removal tool.

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?

Two short sentences, zero filler, with the core action front-loaded and the key parameter behavior immediately after. Every sentence earns its place.

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?

An output schema exists, so return values need not be described. However, for a destructive tool with no annotations and 0% schema coverage, the description omits how a title/episode is targeted and what happens after removal, leaving the agent under-informed.

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% across four parameters, and the description only explains subtitle_id's omission semantics. The roles of imdb_id, season, and episode (and their defaults of 0) are left entirely undocumented, so the description does not compensate for the coverage gap.

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 gives a specific verb and resource: 'Stop serving subtitles for a title,' which an agent can distinguish from add_subtitle, list_subtitles, and push_subtitle by contrast. It does not explicitly name those siblings or clarify its boundary against them, so it falls short of a 5.

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 only conditional guidance is 'Omit subtitle_id to remove them all,' which tells the agent how to broaden the operation but not when to choose this tool over alternatives like push_subtitle or add_subtitle. Usage is implied rather than stated, and no prerequisites or exclusions are given.

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