stremio_addon_health_check

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

With no annotations, the description carries the full disclosure burden. It does disclose scope and that it performs reachability/latency measurement (implying outbound network calls and possible timeouts), but says nothing about read-only safety, expected duration with many addons, rate limiting, or how failures are represented.

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?

A single front-loaded sentence with no filler. The verb and scope are stated immediately and every word 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?

For a zero-parameter diagnostic with an output schema covering the return shape, the description supplies enough to invoke it correctly. It could be slightly stronger by noting the network-call nature and that latency results depend on live reachability.

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?

The tool takes zero parameters, so there are no argument semantics to document. The baseline of 4 applies; the description correctly implies the tool operates on the full installed set with no filtering input.

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 (Check) and resource (every installed addon's manifest reachability and latency). The plural 'every installed addon' implicitly distinguishes it from stremio_get_addon_manifest (single addon) and stremio_check_addon_upgrades (version currency), though no sibling is named 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?

Usage is implied — an agent can infer this is the diagnostic tool for verifying addon connectivity. However, there is no explicit when-to-use framing, no prerequisites, and no reference to alternatives such as stremio_list_addons or stremio_get_addon_manifest.

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