stremio_get_addon_manifest

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond the bare action. It does not say whether addon_url is a full HTTP URL or an addon id, whether the call hits the network and can time out or fail on unreachable addons, or that the operation is read-only and non-mutating.

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?

One short sentence that front-loads the fetch action and adds the summarize behavior without padding. It is efficient, though the extreme brevity is also the source of the missing detail in other dimensions.

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?

With an output schema present, the description needn't explain the return shape, and it gestures at the summarization outcome. However, for a tool whose only parameter is completely undocumented, the description should have covered the addon_url format at minimum, leaving a real gap for a direct-invocation tool.

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% and the single parameter addon_url has no description at all, so the description must compensate. It adds zero clarification on the expected URL/identifier format, which is the one thing an agent could easily get wrong.

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 (fetch) and resource (Stremio addon's manifest) plus an outcome (summarize what it can do). An agent can tell this apart from the general stremio_list_addons or stremio_search_addons, though it never names the related stremio_addon_health_check or stremio_check_addon_upgrades siblings it could be confused with.

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?

There is no statement of when to use this versus inspecting an addon via stremio_show_addon, stremio_addon_health_check, or stremio_list_addons, and no prerequisites. The agent must infer from the name alone that this is for interrogating a single addon's capability declaration.

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