stremio_reorder_addons

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

With no annotations, the description carries the full burden. It usefully discloses partial-update semantics (omitted ids keep relative order behind the passed ones) and the downstream effect on stream results, but says nothing about persistence, whether the change is reversible, or permission/error behavior for what is implicitly a mutation.

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 short sentences, front-loaded with the core action, then the partial-input rule, then the motivation. Every sentence earns its place with no filler.

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 not be explained, and the single-parameter surface is well covered. The only shortfall is the absence of any persistence/reversibility note on a mutation tool with no annotations.

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% and the sole parameter is just 'array of strings' in the schema. The description compensates by explaining that the list is a partial ordering, that position encodes priority, and that omitted addons are preserved behind the passed ones — meaning well beyond the schema.

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 (set/reorder addon query order) and clarifies the direction convention (highest priority first). It is clearly distinguishable from siblings like stremio_install_addon, stremio_list_addons, and stremio_configure_addon.

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 explains the effect (moving a preferred provider to the front changes what plays) which implies when to reach for it, but it never names an alternative tool or states when not to use this versus stremio_install_addon / stremio_configure_addon / stremio_apply_addon_profile. Usage is inferable but not explicit.

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