stremio_next_unwatched_episode

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

With no annotations, the description carries the full burden. It adds some behavioral context: 'regular episode' implies specials are excluded, and 'synced library history' names a data prerequisite. However it never clarifies whether the operation is read-only or mutating, or what auth it needs, leaving the safety profile unclear.

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 tight sentence with the core action front-loaded and no filler. It is efficient, though its brevity is arguably the cause of the missing prerequisite and parameter detail elsewhere.

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 tool with two undocumented parameters, no annotations, and 0% schema coverage, the description does too little: it never addresses imdb_id, the include_unreleased flag, or the sync prerequisite's practical meaning. The output schema covers return values, but the invocation-relevant context is largely absent.

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 description mentions no parameters at all. Neither imdb_id nor the meaningful include_unreleased toggle (which changes what 'first unwatched' returns) is explained anywhere, so the agent must guess at their semantics.

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 ('Resolve') and resource ('first unwatched regular episode') plus mechanism ('using synced library history'). It is clear on its own, but does not distinguish itself from siblings like stremio_continue_watching or stremio_upcoming_episodes, which an agent could easily confuse it with.

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 phrase 'using synced library history' hints at a prerequisite (history must be synced), but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool. The agent is left to infer whether this or stremio_continue_watching / stremio_upcoming_episodes is the right choice.

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