radarr_get_config_importlist

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

readOnlyHint: true is consistent with 'List', but the description adds no extra behavioral context beyond this annotation. It does not clarify whether this returns a config object or the actual list of import lists, which is critical for correct use.

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 one short sentence, but it is under-specified rather than concise. It lacks essential meaning and duplicates a sibling tool's name, so it fails to earn its place despite being short.

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 and zero parameters, the description is too vague to be complete. It does not clarify the resource being read, which is especially problematic given overlapping sibling tool names. A clear statement about config vs. list 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?

The input schema has zero parameters and schema coverage is 100%, so the baseline of 4 applies. There are no parameter details needed, and the description does not need to compensate for any missing schema information.

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 'List import lists' exactly matches the sibling tool radarr_list_importlist, creating ambiguity. The tool name 'radarr_get_config_importlist' suggests it retrieves import list configuration, not the lists themselves, so the description is misleading and fails to distinguish from siblings.

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 radarr_list_importlist or radarr_get_config_importlist_by_id. The description offers no context or exclusions, making it easy to select the wrong tool.

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