stremio_install_addon

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

With no annotations, the description carries the full burden and does well: it discloses account-level scope ('shows up on every signed-in device'), idempotent upgrade-in-place behavior on reinstall, and the ordering effect of position. It omits auth/prerequisite requirements and any failure modes, which keeps it short of a 5.

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?

Front-loaded core action, then effect, then parameter semantics — a sensible order with no filler sentences. The device enumeration is slightly verbose but serves a real scope-disclosure purpose.

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 description covers the mutation's effects, idempotency, and ordering. Minor gaps remain: how to obtain a manifest URL, and whether installation requires the account to be authenticated.

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%, so the description must compensate — and it does for position ('0 is queried first; -1 appends'), which is the non-obvious parameter. manifest_url is only implied to be a manifest endpoint URL rather than an addon id or name, leaving a small format 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?

The first sentence gives a specific verb (install), resource (addon), and target (the Stremio account), plus the identifying mechanism (manifest URL). An agent can distinguish this from siblings like stremio_uninstall_addon, stremio_search_addons, or stremio_reorder_addons without opening 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?

The description implicitly routes the agent by clarifying what reinstall does and how position affects query order, but it never explicitly says when to pick this over alternatives (e.g., find a manifest URL via stremio_search_addons first, or configure with stremio_configure_addon). Usage is inferable rather than stated.

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