stremio_desktop_open

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

No annotations are provided, so the description carries the full disclosure burden. It never states whether Stremio desktop must already be running, what happens if it is not (does it fail, or launch it?), or whether this is purely UI navigation with no playback side effect. For a tool whose name implies an OS-level action, these prerequisites are the key missing behavioral facts.

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 compact sentences with the primary action front-loaded, then the two invocation modes in parallel structure. Every clause carries information; nothing is padding.

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 page enum and id formats are covered. Still missing are the undocumented content_type parameter and the unexplained dependency on the local desktop client being installed and running, which leaves the definition only partially complete for a 5-parameter tool.

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 description must compensate, and it largely does: it explains imdb_id format ('tt1375666'), the season/episode pairing for series, and enumerates the valid page values ('addons', 'library', 'board', 'search', 'settings'), none of which appear in the schema. The fifth parameter, content_type, is never mentioned despite defaulting to 'movie'.

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: 'Open a title, or a named page, in Stremio desktop on this machine.' The dual mode (title via imdb_id vs. named page) is made explicit. It does not differentiate itself from close siblings like stremio_desktop_launch or stremio_desktop_play, 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?

Gives clear invocation context for both branches: pass imdb_id (plus season/episode for series) or pass one of the named pages. However, it offers no when-to-use-this-versus-alternatives guidance, and the crowded sibling set (desktop_launch, desktop_play, desktop_download) makes that omission meaningful.

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