Sonarr Get Episodes

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

With no annotations provided, the description solely bears the responsibility for behavioral disclosure. However, it only states 'List episodes' without revealing any traits such as pagination, filtering, or response structure. This is insufficient for a tool with 11 parameters.

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 short (one sentence), but it sacrifices informativeness for brevity. It fails to earn its place by not adding value beyond the name.

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 complexity (11 parameters, no output schema, no annotations), the description is critically incomplete. It does not explain how to use pagination, what the response looks like, or any caveats.

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 11 parameters with 0% schema description coverage. The description adds no explanation for any parameter, leaving the agent to infer meaning from names alone. For example, 'seriesId', 'to', 'from', 'page', 'limit', etc., are not clarified.

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 verb 'List' and the resource 'episodes for a Sonarr series', making the purpose unambiguous. It distinguishes from sibling tools like sonarr_get_episode_files or sonarr_get_series by specifying 'episodes' and 'series'.

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, nor any indication of when not to use it. The description lacks context for selection.

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