sonarr_create_importlist

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

The description says 'WRITE: this modifies your Sonarr instance' which aligns with the readOnlyHint false annotation but adds little beyond it. There is no disclosure of side effects, prerequisites, or specific behaviors; the annotation already conveys the write nature.

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 very brief and front-loaded with the action, using just two sentences. It avoids unnecessary verbiage, though it is arguably too sparse for a create operation with flexible parameters.

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 flexible body parameter and associated schema, but the description omits any reference to required fields, examples, or related schema tools like sonarr_list_importlist_schema. The presence of an output schema is noted but not visible, so the description does not adequately cover the tool's context.

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 input schema has two parameters (body and force_save) with 0% description coverage, and the description does not mention either parameter. It provides no guidance on what the body should contain or how force_save behaves, leaving the agent without essential information for 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?

The description clearly states 'Create import lists' which is a specific verb and resource. It does not explicitly differentiate from siblings like sonarr_create_importlist_action or sonarr_create_importlist_test, but the core purpose 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 guidance is provided on when to use this tool versus alternatives such as sonarr_create_importlist_test or sonarr_update_importlist. The description simply states the action without context or exclusions.

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