sonarr_update_importlist

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

The description explicitly warns 'WRITE: this modifies your Sonarr instance', which aligns with annotations (readOnlyHint=false) and adds a human-readable caution. However, it does not disclose potential side effects, reversibility, or permissions needed, leaving the agent with only minimal behavioral insight beyond the annotation's basic read/write hint.

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?

The description is two short sentences: the first states the action, the second adds a write warning. Both are succinct and front-loaded, with no fluff. It is concise but somewhat under-specified for the tool's complexity.

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?

The tool has a required id, a nested body object with additionalProperties, and a force_save flag, yet the description explains none of these. The lack of parameter guidance and usage context makes it inadequate for an agent to correctly construct a call without additional external knowledge.

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 description does not explain any parameters (id, body, force_save). It provides no information about what 'body' should contain or how 'force_save' behaves, leaving the agent to guess from parameter names alone.

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?

The description clearly states the action ('Update') and the resource ('import lists'), which is specific enough to distinguish from list/create/delete operations. However, it does not explicitly differentiate between updating a single import list versus the bulk update tool (sonarr_update_importlist_bulk), though the required 'id' parameter implies single-item operation.

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?

The description provides no guidance on when to use this tool versus alternatives like sonarr_update_importlist_bulk, sonarr_create_importlist, or sonarr_get_importlist. It lacks context about prerequisites or the appropriate scenario for a single update.

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