get_shows_by_id_next_episode

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

The annotations already signal read-only, idempotent, and non-destructive behavior. The description adds no behavioral nuance beyond the trivial get operation, such as what defines the 'next' episode, authentication requirements, or edge cases like a show with no next episode.

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 compact and front-loaded: a one-sentence purpose, the HTTP route, and the two parameters. There is no filler or repetition beyond what is structurally useful.

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 2-parameter read operation with an output schema and safety annotations, this is close to adequate. However, it lacks the semantics of 'next episode' and any guidance about choosing this over get_shows_by_id_last_episode, leaving ambiguity for an agent.

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 schema has 0% description coverage, so the description carries the burden. It does add that id is an id/slug and that extended controls additional response information, but it leaves the acceptable values of extended unspecified and only weakly explains its effect.

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?

"Get next episode." clearly identifies the operation and the route /shows/{id}/next_episode names the resource. It is clear enough to distinguish from most siblings, but it does not explicitly separate itself from get_shows_by_id_last_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 guidance is given for when to call this endpoint versus alternatives, especially the closely related get_shows_by_id_last_episode. The one-line description implies a use case but does not state prerequisites, exclusions, or when another tool is preferable.

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