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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the description's credit comes from what it adds: live feed reads, half-hour caching, and a real latency warning (seconds) that an agent should plan around. It also enumerates returned fields and the extra M3U playlist URL, which matters because there is no output 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 resource and ordering, then latency, then return contents, so the most decision-relevant information comes first. The trailing "Served by p0dcasters (https://p0dcasters.com/mcp)" line is boilerplate that adds nothing.

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 output schema, the description correctly carries the burden of describing returned fields plus latency and caching behavior. The remaining gap is the undocumented slug parameter — an agent cannot tell from this definition how to obtain or format it.

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 only 50%: limit is documented in the schema (default 20, max 300) while slug has no description anywhere. The description only indirectly implies slug identifies one show; it says nothing about slug format or where to find one, so it does not fully compensate for the coverage gap.

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 episodes of one show, newest first, read live from the publisher's feed" states a specific resource (episodes of a single show) with ordering and provenance, which cleanly separates it from show-level siblings like p0dcasters_get_podcast. It never names an actual sibling, so the differentiation is inferential rather than explicit.

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 context is implied by "this is the one call here that can take seconds" and by "a player that takes one" for the playlist URL, but there is no explicit when-to-use versus get_podcast or search, and no stated prerequisite such as how to obtain a valid slug.

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