get_upcoming_episodes

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

With no annotations, the description carries the full burden and does substantial work: default 7-day window capped at 60, only monitored shows returned by default with the excluded count reported, seasons premieres/finales/ downloaded state flagged, and the warning that the returned rows are exactly what the user sees. It omits explicit read-only confirmation, pagination behavior, and auth needs, but adds real context beyond any structured field.

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 core purpose and the default-mode answer are front-loaded, and each sentence carries operational content rather than filler. It is dense and somewhat long, but nothing reads as redundant padding.

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?

There is no output schema, yet the description explains the return shape (grouped by day, premieres/finales flagged, already-downloaded marked) and the default filter semantics. An agent has enough to answer correctly without probing further.

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 coverage is 100%, so the baseline is 3, but the description adds meaning: how 'days' interacts with the no-title mode, what 'title' returns when nothing is scheduled, why 'year' disambiguates same-named shows, and the operational reason the monitored filter must reflect the exact filter used. That is genuine value beyond the schema text.

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 ('What TV episodes are coming, from Sonarr's calendar') and cleanly separates two modes: a calendar view by default and a per-show lookup when a title is given. It does not name or contrast with any sibling such as get_on_deck, search_episodes, or check_series_status, so it falls short of full sibling differentiation.

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?

Gives explicit use conditions for both modes ('what's on this week?' without a title; 'when does <show> come back?' with one) and prescribes exactly when to use each monitored filter value. It stops short of pointing to alternative tools for adjacent questions, so context is clear but alternatives are unnamed.

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