stremio_upcoming_episodes

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 discloses the library scope but omits meaningful behavior: the actual window defaults to 90 days despite "soon," results are capped at 50, and no auth/rate-limit context is given. A mutation isn't involved, but for an unannotated tool this is thin.

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, stating the action and the scope immediately. Nothing in the sentence is redundant or misplaced.

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 no prose, but the two visible parameters are undocumented in both schema and description and there are no annotations to compensate. For a time-windowed list tool, the semantics of the window and cap are exactly what an agent needs and they are 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 neither parameter is mentioned in the description. "Releasing soon" vaguely gestures at the days window, but the agent gets no explanation of what days means, its 90-day default, or that limit caps the returned episodes.

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 and resource: "List episodes releasing soon for series in the account library." The library scoping is clear and the concept is distinct from stremio_next_unwatched_episode, but the description never names or contrasts that adjacent sibling, so differentiation is left to inference.

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 "releasing soon for series in the account library," which tells the agent the population being searched, but there is no explicit when-to-use guidance, no stated prerequisites, and no routing away from stremio_next_unwatched_episode or stremio_continue_watching.

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