stremio_browse_catalog

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

With no annotations, the description carries the full burden. It signals the catalog is 'public' (no auth implied), but says nothing about pagination behavior (the skip param), result limits, or rate constraints, which matters for a paged browse operation.

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 efficient sentence with the resource and filter front-loaded. No wasted text, though it is arguably too terse for the information it omits.

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, but the tool still lacks sibling differentiation and any explanation of the three undocumented parameters. For a discoverability-focused catalog tool with three params at 0% coverage, this is insufficient.

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%, so the description must compensate. It only addresses genre filtering and leaves skip (paging) and content_type (movie vs series) entirely unexplained, even though content_type defaults to 'movie' and would silently constrain results.

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 (browse) and resource (public Cinemeta top catalog), which is more than a tautology. However, it does not differentiate from siblings like stremio_search_all_catalogs or stremio_search, so an agent cannot tell which catalog tool to pick without inspecting schemas.

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?

No guidance on when to use this versus stremio_search or stremio_search_all_catalogs. It implies a 'top' listing but never states the conditions that select this tool or any exclusions.

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