stremio_search_addons

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

No annotations are provided, so the description carries full burden. It discloses a non-obvious behavioral constraint: addons flagged configuration_required cannot be installed directly and must be configured in a browser to obtain the real manifest URL. It says nothing about rate limits, pagination, or whether results include uninstalled vs installed state.

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?

Short, front-loaded, and every sentence carries distinct information: purpose, empty-query behavior, next step, and the configuration caveat. Only minor density in the final sentence keeps it from perfect.

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 no explanation, and the description covers purpose, usage, hand-off, and the key installation caveat. The gap is the undocumented 'limit' parameter and no note on result volume or pagination.

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 fully explains 'query' (empty string lists the directory) but never mentions 'limit' or its default/cap, leaving half the parameters undocumented in both schema and description.

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 and resource: search the official Stremio addon directory for addons to install. The 'directory' framing implicitly distinguishes it from stremio_list_addons (installed addons), though no sibling is named explicitly.

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?

Gives explicit when-to-use behavior (empty query lists the whole directory), states the downstream action (pass a returned transportUrl to stremio_install_addon), and warns about the configuration_required exception. That is when, how, and the caveat in three sentences.

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