sonarr_get_episodes

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

With no annotations, the description carries the full burden. "Get" implies a safe read, and it discloses the return payload (air dates, file status, monitoring status), which is genuinely useful given there is no output schema. It omits auth requirements, pagination, and whether the list is ever truncated for large series.

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?

Two short sentences, purpose front-loaded, no filler. Efficient, though the second sentence could carry more routing value instead of only describing the return.

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?

For a simple two-parameter read tool with no output schema, the description adequately covers what it does and what comes back. It is thin on usage context and sibling differentiation, which matters given a crowded family of episode/series retrieval tools.

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 description coverage is 100%, so both seriesId and the optional seasonNumber are already documented in the schema. The description adds nothing about parameter format or the filtering behavior beyond what the schema states, so the baseline 3 applies.

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?

States a specific verb and resource ("Get all episodes for a specific series") and adds what is returned. It is clear, but it never names the sibling sonarr_get_episode (singular) or sonarr_search_episodes, so an agent must infer the boundary between 'all episodes for a series' and 'one episode'.

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 when-to-use guidance and no alternatives named. The agent gets no signal on when to prefer this over sonarr_search_episodes or sonarr_get_episode, leaving selection to inference from the name alone.

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