stremio_streaming_server_streams

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

With no annotations, the description carries the full burden. It discloses the runtime prerequisite (desktop app running) and implies a read-only inspection, which is valuable. But it does not state permission/auth needs, whether any state is affected, or how results are scoped beyond the info_hash.

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 sentences with the purpose front-loaded and the parameter guidance following. No filler; the only minor cost is the awkward line wrapping, which is cosmetic rather than substantive.

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. Combined with the stated prerequisite and parameter behavior, the definition is complete enough to call correctly, with the only gap being no explicit routing to sibling tools.

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: it explains that info_hash selects a single engine while an empty value inspects all. This is exactly the semantics an agent needs for the one required-free parameter.

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 (List) and concrete resources (active torrent engines, transfer rates, per-file download progress). It is clearly distinguishable by content from write-oriented siblings like purge_cache, though it never names an alternative for routing.

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?

It gives a precondition (Stremio desktop app must be running) and explains the two usage modes for the parameter, which is helpful. However, it never says when to choose this over sibling diagnostics like stremio_streaming_server_cache or stremio_desktop_status, so usage is only implied.

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