get_show_latest_episode

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

There are no annotations, so the description carries the full burden. It does disclose useful behavior: it returns the newest episode, includes duration/description/resume point, and defaults to 'concise' prose. It does not mention potential pitfalls like missing episodes, availability behavior, error cases, or authentication needs, but the read-only GET behavior is at least implied.

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 a single dense sentence with a memorable use-case phrase and no filler. Key information is front-loaded, and the default behavior statement is efficient.

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 single-object GET with fully described parameters, the description plus schema covers the essential information: what is returned, the input identifiers, and the output format options. The absence of an output schema is mitigated by naming the main returned fields, though it does not elaborate on the 'detailed' or 'json' shapes.

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 the input schema already fully documents show_id, market, and response_format. The description adds little beyond restating the default response format and the fields returned; it does not deepen understanding of the parameters themselves.

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 uses a specific verb and resource: 'Return the single newest episode of a show' and names the exact output fields, making the tool's function immediately clear. The phrase 'what dropped last?' reinforces the intent and distinguishes it from broader episode-listing siblings like get_show_episodes or show_episode_search.

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?

The description conveys the use case ('what dropped last?') and implies this is the right tool when only the single newest episode is needed. However, it does not explicitly mention alternatives or conditions where other sibling tools such as get_show_episodes, get_newly_released_episodes, or show_episode_search would be more appropriate.

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