radarr_bulk_update_importlist

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

The description adds 'WRITE: this modifies your Radarr instance,' which aligns with the annotations (readOnlyHint=false, destructiveHint=false). It reinforces that this is a write operation, but adds no further context about side effects, required permissions, or what specifically gets modified. With annotations already covering the write nature, the added value is minimal but not contradictory.

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 extremely concise and front-loaded with the primary purpose ('Bulk update import lists'). The WARNING is a single short sentence that adds necessary emphasis without unnecessary verbosity. No wasted words.

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?

Despite having an output schema, the description lacks critical input context. It does not specify how the bulk update works, what fields are accepted in the body, or how to provide multiple import list updates. Given the loose body schema and complete absence of parameter guidance, the description is inadequate for correct invocation.

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?

The schema has a single 'body' parameter with additionalProperties allowed, but no field documentation. Schema description coverage is 0%, and the description does not explain what the body should contain (e.g., IDs, fields to update). The tool is unusable without knowing the expected payload structure.

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 'Bulk update import lists' with a specific verb and resource. This distinguishes it from sibling tools like radarr_update_importlist (single update) and radarr_bulk_delete_importlist (delete operation). The intent is unambiguous.

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 explicit guidance on when to use this tool versus alternatives. It does not mention that single updates should use radarr_update_importlist or that bulk operations are for multiple lists. The WRITE warning is generic and does not help select among similar tools.

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