get_newly_released_episodes

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly communicates the operation is a collection/merge, states the ordering ('newest-first'), the tagging behavior ('tagged with their show'), and the default date cutoff ('last 7 days'). It does not disclose potential cost/latency of scanning all saved shows, but the inclusive date floor and merged output are well covered.

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 sentences, no filler. The core action and scope are front-loaded, and the appositive '— the unified new-episode inbox' efficiently positions the tool's purpose. Every clause earns its place.

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 tool with four optional parameters and no output schema, the description gives enough context to select it correctly: it states scope, ordering, tagging, and the default window. It does not describe the return structure, but the response_format parameter partially addresses that, and the core decision-making context is complete. Minor gap: no warning about the potential breadth of 'ALL saved shows.'

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 parameters are already well documented with defaults and meanings. The description adds only the 'last 7 days' default phrasing, which mirrors the schema's 'Default 7 days ago' and reinforces usage but does not meaningfully enrich parameter understanding beyond the schema.

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 names a specific verb ('Collect'), a specific resource ('episodes released since a date'), and a clear scope ('across ALL saved shows'). It also adds distinguishing behaviors—'merged newest-first and tagged with their show'—and characterizes itself as 'the unified new-episode inbox,' which separates it from single-show tools like get_show_latest_episode or list_show_episodes.

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 implies usage context: it is for getting new episodes across all saved shows at once, and the default 'last 7 days' suggests a recurring inbox-style use. However, it does not explicitly state when to prefer this tool over alternatives (e.g., show_new_episodes, shows_release_calendar) or mention exclusions such as 'use get_show_latest_episode for a single show.'

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