sonarr_get_import_exclusions

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

No annotations are provided, so the description carries the burden of conveying safety. The verb 'List' implies a read-only operation, and the parenthetical explains the meaning of 'import exclusions'. However, it does not disclose return format, pagination, or other behavioral characteristics beyond the bare fact that it returns a list.

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 a single, front-loaded sentence that states the action and the resource. The parenthetical adds useful context without unnecessary verbosity. Every word earns its place.

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 has no parameters, no output schema, and no annotations, the description provides the essential information: it lists import-excluded series and clarifies the meaning. It is complete enough for a simple, parameterless list tool, though it omits any details about the returned fields or potential errors.

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, so the baseline is 4 per the rubric. The description correctly says nothing about parameters because there are none to explain.

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 uses a specific verb ('List') and identifies the exact resource ('series that are excluded from import'). The parenthetical clarification ('blocked from being re-added after deletion') removes ambiguity and distinguishes it from related tools like sonarr_get_blocklist and sonarr_delete_import_exclusion.

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?

The description implies usage by stating what the tool does, but it does not explicitly state when to use it versus alternatives. No mention of when not to use it, nor any reference to sibling tools that might overlap. The context suggests it is for reading exclusions, but explicit guidance is absent.

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