sonarr_get_importlist

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

Annotations include readOnlyHint: true, and the description 'Fetch' is consistent. The description adds no extra behavioral context beyond the annotation (e.g., auth requirements, 404 behavior, or potential side effects), but for a trivial read endpoint the annotation suffices.

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?

One short sentence, front-loaded with the verb. The grammar error ('lists' plural) is a minor blemish; otherwise it is concise and to the point.

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?

Given the tool's simplicity (one parameter, read-only, output schema present), the description is largely sufficient. It misses usage alternatives and doesn't mention the output, but the output schema covers return values. Overall complete for its low complexity.

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 has one unannotated integer parameter (coverage 0%). The description's 'by id' clarifies the parameter's role, but it essentially restates the tool name. It does not provide format, source, or constraints for the ID. For a single obvious parameter, this is minimally acceptable.

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 it fetches a single import list by ID, using the verb 'Fetch' and specifying the resource. The phrase 'single ... by id' distinguishes it from list-oriented siblings like sonarr_list_importlist. Minor grammar issue ('lists' instead of 'list') but meaning 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?

Implied usage is to fetch one item by ID. No explicit guidance on when to use this vs alternatives, nor any mention of using list_importlist to enumerate all lists. The context is clear from the verb and parameter, but no explicit exclusion.

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