stremio_desktop_play

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

No annotations, so the description carries the full burden. It usefully discloses that streams follow installed-addon order then per-addon result order, and that video_id restores saved timeOffset. However, it says nothing about auth requirements, whether the call blocks, or what wait_seconds does behaviorally.

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 front-loaded sentences with no filler; the primary purpose leads and the ordering/selection mechanics follow. Each sentence contributes useful information.

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 explanation, and the ordering semantics are covered. But with 7 params at 0% schema coverage and no annotations, the description should explain content_type values, wait_seconds semantics, and playback failure behavior; it does not.

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 coverage is 0% across 7 parameters, so the description must compensate. It meaningfully explains stream_index (selection from the merged list) and video_id (timeOffset restoration), but leaves season, episode, content_type, imdb_id, and especially wait_seconds undocumented.

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: 'Select an installed-addon stream and start it in Stremio desktop.' The 'in Stremio desktop' scoping distinguishes it from sibling playback tools like stremio_cast_play or play, though no sibling is named 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?

Provides a conditional usage hint (pass video_id for continue-watching items so timeOffset is restored) but gives no guidance on when to prefer this over the many sibling playback tools (stremio_cast_play, play, tv_control). Usage is implied rather than stated.

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