Recent transcripts

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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds return-format context (podcast guids that feed the show tools) and ordering (newest first), plus the resolve_shows cost note. It doesn't state rate limits or pagination, but adds useful behavior beyond the annotations.

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?

Three tight sentences, front-loaded with the resource and scope before the usage guidance. Every sentence contributes, though the final sentence is a mild restatement of the return value already implied by the tag/guid framing.

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, but the description explains what is returned (newest-first episodes with podcast guids usable by the show tools). Annotations cover the safety profile. Combined with 100% schema coverage, an agent has enough to call it correctly, though return field detail is thin.

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%, so both parameters are already well documented. The description connects the returned guids to the show tools, which hints at the resolve_shows use case, but does not add syntax or defaults beyond the schema. 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?

States a specific verb+resource+scope: recently published episodes across all of OP3 carrying a podcast:transcript tag, newest first. This clearly distinguishes it from the sibling download/audience tools, which the description explicitly contrasts against ("read transcripts rather than count downloads").

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 when-to-use context: find podcasts with machine-readable episodes, the shortlist for anything that needs to read transcripts. It contrasts the use case against download-counting siblings, but doesn't name a specific alternative tool the way the top-tier example does, so it stops short of explicit routing.

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