stremio_desktop_download

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

No annotations, so the description carries the full burden and largely meets it: it discloses the remote read of the downloads page, the on-disk side effect and location (Downloads folder), and the elevated-privilege caveat for installation. It omits edge behavior such as overwriting an existing file or failure modes.

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 tight sentences, front-loaded with the action and resource, then mechanics, then the one parameter override and the scope caveat. No filler and every sentence adds information.

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 explained, and the description covers defaults, platform values, side effects, and the admin-password limitation. Minor gaps around overwrite behavior and any network/rate constraints keep it short of complete.

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, and it does for target_platform by enumerating the accepted values ('Darwin', 'Windows' or 'Linux') and clarifying the default is the current machine. The destination parameter is only implied via 'saves it to the Downloads folder', so it is not fully documented.

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+resource ('Download the Stremio desktop installer') with explicit mechanics (reads official downloads page, picks the .dmg/.exe/.deb matching architecture). An agent can distinguish it from siblings like stremio_desktop_launch or stremio_desktop_status purely from this text.

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?

Clear context: it tells the agent to pass target_platform to fetch for a different machine, and states that running the installer is left to the agent because it requires an admin password. It draws the boundary with the launch/install step but never names the sibling tool responsible for that step, leaving a small inference gap.

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