stremio_desktop_show_addon

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 usefully discloses that this is a UI-level navigation (opens a review page rather than installing), but omits prerequisites such as whether the Stremio desktop app must be running or paired, and whether any state changes occur.

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 short sentences, purpose front-loaded, alternative immediately after. No filler or restatement of the tool name.

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 routing to the alternative tool is complete. However, with zero parameter documentation and no annotations, an agent still lacks the argument semantics and the desktop-app prerequisites needed to invoke this reliably.

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%, yet the description never mentions either parameter. manifest_url is the sole required argument and content_type carries a default ('movie') whose meaning and valid values are unexplained anywhere, so the description fails to compensate for the coverage gap.

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 an addon's install page in Stremio desktop') plus the intent ('so it can be reviewed'). It is clearly separable from siblings like stremio_desktop_open, stremio_desktop_launch, and stremio_install_addon without inspecting 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?

Explicitly names the selecting condition ('addons that need configuring by hand') and the alternative for the opposite case ('For a headless install that also reaches every other device, use stremio_install_addon instead'). This is a textbook when/when-not with named sibling.

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