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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral context: the trailer is excluded, results are ordered newest-first, and each row reports whether a transcript is searchable yet. It does not mention pagination or any result-size cap.

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?

One dense sentence, front-loaded with the resource and scope before the field list. No filler, no restatement of the title.

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?

With no input parameters, no output schema, and read-only annotations, the description carries the remaining burden and does so: it defines the population, ordering, exclusions, and the exact contents of each returned episode.

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?

Zero parameters, so the baseline is 4 and there is nothing to disambiguate. The description goes further by enumerating the returned fields (number, title, guest, company, release date, length, link, transcript-searchable flag), which is useful even though it describes output rather than input.

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 ('List ... episodes') plus meaningful scope: every published episode, trailer excluded, newest first. This implicitly separates it from get_episode (single item) and search_podcast (query-driven), but it never names those siblings, so it falls short of the 5-level explicit 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?

Usage is only implied: the catalog-style scope ('Every published ... episode, newest first') suggests browsing the full back catalogue rather than searching, but there is no explicit when-to-use, when-not-to-use, or named alternative such as search_podcast for filtered queries.

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