stremio_list_addons

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

With no annotations, the description carries the burden. It does add genuine behavioral context beyond the schema: the addons are account-wide ('every signed-in device sees') and order is significant because Stremio queries addons top to bottom. However, it omits auth requirements and any note that this is a safe read, leaving the operation's safety profile unstated.

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 short sentences, front-loaded with the core action. The scope sentence and the ordering note each earn their place by informing how the agent should interpret the result.

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 the description need not explain return values, and there are no parameters to document. Given the simplicity, the description is nearly complete; only the absence of any read-safety or auth context keeps it from being fully sufficient.

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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly implies nothing needs to be supplied to scope the call.

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 ('List the addons installed on the Stremio account'), which is clear and distinct from write-oriented siblings like stremio_install_addon or stremio_reorder_addons. It does not explicitly distinguish itself from stremio_search_addons, but the 'installed on the account' scope does that implicitly.

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 implied rather than stated: the agent can infer it should call this to inspect currently installed addons, but there is no explicit when-to-use, when-not, or named alternative. No prerequisites or follow-up guidance are given.

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