stremio_save_addon_profile

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

With no annotations, the description carries the full behavioral burden. It implies a persisted write (a saved profile), but discloses nothing about authentication, what happens on a name collision, whether an existing profile is preserved or destroyed, or how the snapshot relates to later apply/restore calls.

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, front-loaded with the verb and the resource, with no filler. It is appropriately sized for the operation, though it is terse enough that the overwrite behavior has no place to live.

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, but for a mutation tool with no annotations and 0% parameter documentation, the description is under-specified: overwrite behavior and the profile-lifecycle relationship to stremio_apply_addon_profile / stremio_list_addon_profiles are missing.

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 neither parameter is documented structurally. The description hints at the required `name` ('under a name') but says nothing at all about `overwrite` — the one parameter whose semantics (fail vs. replace an existing profile, default false) are most consequential for correct invocation.

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?

Clear verb+resource: 'Save the account's current ordered addon collection under a name' states exactly what is persisted (the ordered addon collection) and the naming requirement. It does not, however, name the sibling it pairs with (stremio_apply_addon_profile) or distinguish itself from stremio_reorder_addons / stremio_restore_default_addons, which also mutate the addon collection.

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 when-to-use, when-not-to-use, or alternative guidance is given. An agent must infer that this is a snapshot operation whose counterpart is stremio_apply_addon_profile, and nothing states prerequisites (e.g., whether addons must already be installed/reordered first).

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