stremio_get_meta

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

No annotations are provided, so the description carries the full burden. It does disclose the return payload (metadata plus episode list for series), which is useful, but says nothing about authentication, rate limits, failure modes, or whether lookups work for non-IMDb ids.

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, key input, and notable return content all appear immediately.

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-value explanation is not required, and the read-only nature is self-evident from 'Get'. However, the undocumented content_type parameter is a real gap for a tool that must serve both movies and series.

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% for both parameters. The description clarifies imdb_id as the lookup key but never mentions content_type, whose default of 'movie' matters greatly since series metadata requires switching it — the phrase 'episode list for a series' hints at series support without explaining how to enable it.

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 (Get) and resource (full metadata for a title) scoped by an identifier (IMDb id), and notes it includes a series episode list. It does not explicitly differentiate itself from siblings like stremio_search or stremio_get_streams, but the purpose is unambiguous.

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 only implied: the required imdb_id suggests it is called after a search/browse step, but the description never states when to prefer it over stremio_search, stremio_browse_catalog, or stremio_get_streams, nor any prerequisites.

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