stremio_check_addon_upgrades

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

No annotations are provided, so the description carries the burden, and it does useful work: it flags a safe default (inspect) versus a mutation that reinstalls every newer manifest 'in one guarded account collection update'. It stops short of stating auth/prerequisites or reversibility, but the safety profile is well communicated.

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 tight sentences, no filler, with the inspect/apply distinction front-loaded. Every clause earns its place.

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. For a one-parameter tool the description covers the essential behavior; only minor gaps remain around what 'guarded' entails and any login prerequisites.

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 single parameter is documented only as a boolean titled 'Apply' with default false. The description fully supplies the missing semantics by defining what true and false actually do.

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: comparing installed addon versions against live manifests, with an optional upgrade action. This clearly separates it from siblings like stremio_addon_health_check and stremio_install_addon, though it never names an alternative explicitly.

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 direct mode guidance: 'Leave apply false to inspect' vs 'Set apply true to reinstall...'. Clear context for choosing behavior, but no exclusions or references to related tools for when this is not the right choice.

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