Newest episodes in your library

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

Annotations already declare safe read-only idempotent behavior. The description adds meaningful context beyond annotations by noting results come from a cached local database view reflecting the last Podcasts-app refresh, and that ordering is newest first. This helps an agent understand the tool's freshness limitations.

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 two sentences with no waste: the first states the core behavior and ordering, the second adds a crucial staleness caveat. It is front-loaded and easy to parse.

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 read-only listing tool with four optional params and no output schema, the description covers what is returned, in which order, and from which data source. The local-cache caveat is especally valuable because it prevents relying on this tool for live-feed data, and annotations already cover safety and idempotency.

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?

All four parameters have concise descriptions in the input schema, so the schema carries the full parameter-documentation burden. The tool description reinforces the overall concept but does not add parameter-specific detail beyond what the schema already provides.

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 states a specific action and resource: listing the most recently published episodes across shows you follow, newest first. It also differentiates from sibling tools like list_saved_episodes by emphasizing followed shows rather than saved 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 provides useful context: it returns the local database's view and may lag live feeds, implying it is for library-state queries rather than realtime checks. However, it never explicitly names alternatives such as get_feed or says when not to use this tool.

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