stremio_search

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

With no annotations, the description carries the full behavioral burden. It does add one useful trait beyond the schema — the data source is the public Cinemeta catalog, implying no auth and read-only — but it says nothing about result ordering, pagination, or how 'limit' behaves. It is aware of one trait while omitting the rest.

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 the verb and resource first and zero filler. Nothing redundant and nothing that could be trimmed without losing meaning.

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?

The tool has a near-duplicate sibling (stremio_search_all_catalogs) that the description never distinguishes, and all three parameters are undocumented in the schema while the description only partially covers two of them. The output schema does relieve it of explaining return values, but the remaining gaps leave an agent guessing on routing and arguments.

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. 'by name' maps to query and 'movies or series' hints at content_type, but it never states the accepted content_type values (movie/series) nor what limit controls or its default. Two of three parameters get only partial coverage.

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?

Specific verb (search) plus resource (movies/series) and even the backing catalog (Cinemeta), which lets an agent distinguish this from a generic catalog browse. It stops short of naming the near-identical sibling stremio_search_all_catalogs, so the differentiation is implicit rather than stated.

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?

The phrase 'through the public Cinemeta catalog' implies the scope condition for using this over a broader catalog search, but no when-to-use, when-not-to-use, or alternative (stremio_search_all_catalogs, stremio_browse_catalog, stremio_get_meta) is named. Usage must be inferred.

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