get_recent_podcast_episodes

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

With no annotations, the description carries the full burden. It discloses return fields, clarifies that transcriptId is a path fragment and episodeId is an Apple store track id, and notes the 'once cached' requirement for transcripts. 'Lists' implies a read-only operation, though an explicit read-only statement would be stronger.

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 three sentences with no filler: purpose, returned fields, and downstream usage. It is front-loaded and every sentence earns its place.

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?

No output schema exists, so the description compensates by enumerating the returned fields and downstream tool links. It could mention ordering or pagination, but the limit parameter is already documented in the schema. Overall, it is sufficiently complete for a listing tool.

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 schema has 100% description coverage for all 5 parameters, so the baseline is 3. The description only summarizes filters ('release date range and/or title query') without adding new semantic detail beyond the schema's already-rich parameter descriptions.

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 'Lists podcast episodes from MTLibrary.sqlite' with optional filters, giving a specific verb, resource, and scope. It distinguishes itself from siblings like get_podcast_transcript and open_podcast_episode by focusing on episode listing/querying.

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?

Provides clear downstream guidance: 'Pass a title to open_podcast_episode, and transcriptId to get_podcast_transcript once cached,' implying this tool is the episode discovery source. It lacks explicit when-not-to-use instructions but gives sufficient context for typical usage.

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