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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral fact beyond that: each returned episode carries the user's read state, which is useful for the agent's follow-up decisions. It says nothing about ordering, pagination, or result limits.

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?

A single front-loaded sentence with the verb and resource first and no filler. Every clause carries information: scope, resource cardinality, and return content.

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?

For a read-only list tool with fully documented parameters and no output schema, the description covers what is listed, for which podcast, over what window, and one key return field. It stops short of describing the episode fields returned or ordering, which the agent would otherwise have to discover by calling 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 description coverage is 100% — days, endDate and podcastSeq all have ranges, formats and defaults documented inline. The description's 'published within a date range' maps onto days/endDate but adds no format or interaction detail (e.g. how days and endDate combine), so baseline 3 is correct.

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?

Specific verb+resource ('List episodes of one podcast') plus explicit scope (date range) and a return-content hint (read status). It clearly implies a single-podcast scope, but never names the obvious overlapping siblings (list_followed_episodes, search_episodes, get_episode) to differentiate itself.

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?

There is no when-to-use or when-not-to-use guidance. Given a sibling set containing list_followed_episodes, list_my_episodes, search_episodes and get_episode, the agent must infer from the name alone which list tool applies, and the description offers nothing to help.

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