stremio_continue_watching

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

With no annotations, the description carries the full burden, and it does disclose the sort order and clarifies that position_ms is the playback stop point usable directly by a player — genuinely useful behavioral context beyond the structured fields. It falls short of stating read-only semantics, auth needs, or limits, which is why it is not a 5.

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?

Three short sentences, front-loaded with the core purpose, and every sentence earns its place by adding scope, framing, or field semantics.

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 low-complexity, single-parameter read tool with an output schema covering return values, the description is nearly complete: purpose, ordering, and field meaning are all present. Only the limit parameter and any auth/read-only expectations are left 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% and the single 'limit' parameter is never mentioned in the description, so it is undocumented everywhere. The parameter is intuitive enough that this is not a severe gap, but the description does nothing to add meaning over the bare schema.

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 ('List') and a precise resource ('part-watched titles with their resume positions'), and even scopes the ordering ('most recent first'). An agent can distinguish it from stremio_get_library or stremio_upcoming_episodes without opening any schema.

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 line 'This is the row Stremio shows on its home board' gives useful framing for what the tool represents, and 'can be handed straight to a player' hints at the playback-resume use case. However, there is no explicit when-to-use vs alternatives, no exclusion of the library/upcoming tools, and no stated prerequisites.

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