sonarr_list_importlist

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

The annotation readOnlyHint=true already establishes the safe read-only nature. The description adds no additional behavioral context, such as whether all import lists are returned, performance considerations, or response structure. With no parameters, there isn't much to disclose, but the description still fails to clarify scope.

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 four words long, entirely free of redundancy. It is appropriately sized for a zero-parameter list operation and every word is informative.

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 combination of readOnlyHint annotation and presence of an output schema makes this minimally viable. However, the description does not explain what an import list is or how this endpoint relates to sibling list/schema tools. Adequate for a simple tool but lacks contextual richness.

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 tool has zero parameters and the schema is complete (empty properties). The baseline of 4 applies since there are no parameters for the description to document or augment.

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 operation (list) and the resource (import lists), making the purpose unambiguous. It implies a collection-returning operation, but doesn't explicitly distinguish from sibling tools like 'sonarr_list_importlist_schema' or 'sonarr_get_importlist'.

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 like 'sonarr_get_importlist' (single item) or 'sonarr_list_importlist_schema' (schema). The description is too brief to convey any contextual usage information.

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