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

Goes well beyond readOnly/idempotent annotations: it discloses that the feed is fetched live, that episodes without a transcript are retained and labelled transcript_status "no_publisher_transcript", and that a show publishing none still returns its episode list. These are non-obvious output behaviors an agent cannot infer from annotations or schema.

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?

Front-loaded with the core question the tool answers, then follow-on sentences for behavior and alternatives. It is dense but every sentence carries distinct information; slightly long, with the status-label sentence bordering on over-explanation.

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?

There is no output schema, and the description compensates by describing the return shape (per-episode transcript links with format, language, URL, plus a transcript_status field for episodes lacking one). Nothing needed to invoke or interpret the result is missing.

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 coverage is 100%, so the baseline is 3; the description adds value by naming the three accepted id forms and pointing to find_podcast_contacts as the origin of show_id, plus clarifying that the episode filter is optional. It does not restate limit semantics, but that is fully covered in 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?

States a precise verb and resource: reads the show's live RSS feed and lists every episode's Podcasting 2.0 <podcast:transcript> links with format, language and URL. It is clearly an inventory/availability tool, not an extraction tool, which distinguishes it from search_podcast_transcript.

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?

Explicitly routes the agent: use this to see which episodes have publisher transcripts, and 'Use search_podcast_transcript to pull timestamped passages from one.' It also names find_podcast_contacts as the source for the show_id/podcast:guid argument, so the agent knows the prerequisite chain.

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