stremio_find_streams

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

With no annotations provided, the description carries the full burden and does disclose meaningful behavior: it queries addons in order, merges results, and reports failing or empty addons separately rather than dropping them. It still omits auth/permission requirements, latency, and how the per_addon cap affects results, so the behavioral profile is incomplete.

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 sentences, front-loaded with the core purpose and followed by useful clarifying context. No obvious padding, though the middle explanatory sentence is more framing than actionable detail.

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 aggregation/error-handling behavior is covered. But with 5 undocumented parameters and no annotations, the definition is not complete enough to guarantee correct invocation without opening the schema.

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% across 5 parameters, so the description must compensate and largely does not. It only loosely implies the title/imdb_id input and says nothing about season, episode, per_addon, or content_type, leaving four parameters undocumented in both schema and prose.

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?

The description states a specific action and resource: it asks every stream addon on the account for a title and merges results, which is clear enough for an agent to understand the aggregation behavior. However, it never distinguishes itself from close siblings like stremio_get_streams or stremio_streaming_server_streams, so an agent cannot tell which stream tool to select from the text alone.

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 contextual framing ('This is what Stremio itself does when you open a title'), which implies the intended use case of fetching playable streams for a title. But it offers no explicit when-to-use versus alternatives and no exclusions relative to the multiple sibling stream/subtitle tools.

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