stremio_remove_from_library

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. It usefully discloses that 'Watch state is kept', which is genuine context for a removal operation (partial rather than total destruction), but it omits auth requirements, reversibility, and side effects on other library metadata.

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, front-loaded sentences with no filler. The operation is stated first and the behavioral caveat second, which is the right ordering.

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 explained. For a simple mutation tool, the description covers purpose and one behavioral trait, but with no annotations and no param docs it leaves auth/permission context and identifier format unaddressed.

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 schema documents nothing about imdb_id. The description doesn't compensate at all—no format, source, or validity info. Only the well-known nature of an 'imdb_id' keeps this from scoring lower; with a single self-evident identifier, a 3 is fair.

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+resource combination: 'Remove a title from the account library.' An agent immediately understands the operation. It does not explicitly differentiate from siblings like stremio_add_to_library or stremio_mark_watched, though the name itself is distinctive.

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 when-not-to-use guidance, no alternatives named. The tool name makes the basic purpose inferable, but the description offers nothing about context for choosing it over related library/mark-watched tools.

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