sonarr_list_episode

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

The readOnlyHint annotation already communicates the safe read-only behavior. The description simply repeats 'List' and offers no additional behavioral traits such as response formats, pagination, or the effect of optional flags like include_series or include_images.

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 appropriately short and contains no fluff, but the brevity borders on under-specification rather than effective conciseness. It is a single, grammatically correct sentence, yet it lacks the useful structure that would make it earn its place in tool documentation.

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 tool has 7 parameters and an output schema, indicating significant complexity. The description provides no contextual details about filtering options, typical use cases, or the relationship to other episode-related tools, making it insufficiently complete for an agent to use the tool correctly.

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?

With 0% schema coverage for 7 parameters, the description was expected to compensate but fails entirely. None of the parameters (series_id, episode_ids, season_number, include_series, etc.) are mentioned or explained, leaving the agent without any semantic guidance for constructing a valid request.

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 episodes' restates the tool name (sonarr_list_episode) without adding any new scope or context. It is essentially a tautology, providing no distinction from sibling tools like get_episode or details about what list operation entails.

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 usage guidance is provided. The description does not mention when to use this tool instead of alternatives like get_episode, how the optional parameters filter results, or any other context for selection. This is a complete absence of guidance.

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