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

Annotations already indicate read-only, idempotent, and open-world behavior. The description adds the list of returned fields and mentions 'funding links (PodcastIndex)', providing contextual details beyond annotations but no new behavioral traits like rate limits or error handling.

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 concise, front-loading the purpose ('Full metadata for a single podcast') and listing key fields in a clear, readable manner. Every element adds value with minimal verbosity.

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 simple parameter (single integer) and presence of an output schema, the description adequately covers the tool's scope. It mentions the source (PodcastIndex) and highlights key metadata fields, making it sufficiently complete for an agent to understand the return value.

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 fully describes the single 'id' parameter with 100% coverage. The description repeats 'by Feed ID' but adds no semantic nuance beyond the schema's own description. Baseline 3 is appropriate.

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 the tool returns 'full metadata for a single podcast' and enumerates specific fields (title, author, RSS URL, etc.). It distinguishes from siblings like 'media.podcast.search' by focusing on a single podcast by feed ID, but does not explicitly differentiate when to use this over related tools.

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 no guidance on when to use this tool versus alternatives (e.g., media.podcast.search, media.podcast.episodes). It lacks prerequisites, exclusions, or usage context beyond retrieving metadata for a known feed ID.

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