Remove list items

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the agent knows this mutates and is repeat-safe. The description adds only the 'static lists' constraint; it says nothing about what happens when an item is absent from the list, whether the removal is partial across movies/shows arrays, or whether error responses are returned.

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?

A single front-loaded sentence with no filler, and the destructive action is stated first. It is efficient, though its terseness leaves real gaps rather than being maximally useful.

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?

There is no output schema, so the description should carry more of the response story for a destructive bulk operation, such as partial-success behavior or confirmation of what was removed. With rich annotations in place, the essentials are covered, but a destructive array-based mutation warrants a bit more.

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 100%, with IMDb/TMDb ID examples already documented, so the baseline applies. The description does not clarify whether the movies and shows arrays are mutually exclusive, whether either is optional alongside required list_id, or how multiple identifiers per object are resolved.

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?

States a specific verb (remove) and resource (movies/shows in a user's static list), which distinguishes it from add_list_items. The 'static lists' scoping also loosely separates it from remove_watchlist_items, though it never names that sibling explicitly.

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?

Usage is implied by the phrasing 'from one of the user's static lists', which hints the target must be a static list rather than the watchlist. But there is no explicit when-to-use guidance, no prerequisites (list ownership, item must exist), and no routing to the nearest alternative, remove_watchlist_items.

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