stremio_apply_addon_profile

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

With no annotations, the description carries the burden and does disclose meaningful behavior: a protected-addon guard runs and an automatic backup is taken before the account write. That tells the agent the operation is destructive but recoverable and that some addons are shielded. It still omits auth/permission requirements and whether the backup can be re-applied.

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?

Two sentences, front-loaded with the effect, followed by the safety behavior. No filler and nothing repeated from the schema.

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?

For a one-parameter mutation tool with no annotations, the description covers the critical unknowns: what is overwritten and that a guard plus backup precede the write. An output schema exists, so return values need no explanation; only the profile-name discovery path is 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 coverage is 0% and the single 'name' parameter has no schema description, so the description must compensate. 'Saved named profile' does indicate that name refers to an existing profile's name, but it does not state the accepted values or how to discover them (e.g., via stremio_list_addon_profiles), leaving a real gap.

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 (Replace) plus the exact resource (the account addon collection) and the source of the new state (a saved named profile). This clearly separates it from stremio_save_addon_profile, stremio_list_addon_profiles, and stremio_restore_default_addons without needing to name them.

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 by 'saved named profile' – the agent infers this is the step that applies a previously saved profile. However, there is no explicit when-to-use/when-not, no mention of the prerequisite that the profile must already exist (stremio_save_addon_profile / stremio_list_addon_profiles), and no routing to the restore-default alternative.

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