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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds context about return fields and source of feed ID but does not disclose additional behavioral traits like ordering or pagination behavior beyond the max parameter.

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 wasted words. The first sentence contains the purpose and return fields, while the second provides parameter guidance. It is front-loaded and 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?

Given the tool has 3 parameters, an output schema, and annotations, the description covers the main aspects: purpose, source of required parameter, and what is returned. It could mention ordering (recent implies by date) and pagination explicitly, but with the output schema present, this is acceptable.

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?

The input schema has 100% description coverage, and the description reiterates the source of the 'id' parameter but adds no new meaning beyond what the schema provides. For example, 'max' and 'since' are already documented 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?

The description clearly states 'List recent episodes for a podcast by feed ID' with a specific verb and resource. It lists the return fields (title, description, publish date, audio URL, duration, season/episode numbers) and distinguishes itself from sibling tools like media.podcast.search, media.podcast.details, and media.podcast.trending by focusing on 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 advises to 'Use feed ID from search or trending results (PodcastIndex)', providing clear context for parameter sourcing. However, it does not explicitly state when to use this tool versus alternatives or when not to use it, though the purpose implies it's for episode listing after obtaining a feed ID.

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