stremio_restore_default_addons

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

With no annotations, the description carries the full burden and does disclose the key behavioral fork: true preserves other addons and fills only missing defaults, while false resets the account to a stock addon list (i.e. removes non-defaults). It does not mention auth requirements or whether existing default addon configs are overwritten.

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 blocks, purpose first, then the when-to-use condition and the parameter behavior. No filler sentences; every line contributes.

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 described, and the single parameter is fully explained. The only gap is operational context such as authentication/prerequisites for modifying an account's addons.

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 does: it spells out the semantics of both keep_installed=true (preserve others, backfill defaults) and false (full reset to stock list). This is more than the bare boolean in 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 (reinstall) and resource (Stremio's seven default addons) plus the target (the account). It is clearly distinguishable from siblings like stremio_install_addon (single addon) and stremio_list_addons, as it is a bulk restoration of defaults.

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 an explicit trigger condition: 'Use this when the addon list is empty or broken.' That is clear context for invocation, though it never names the alternative tools (e.g. install_addon for individual repairs) an agent might weigh against it.

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