op3_recent_transcripts

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds important behavioral context: it returns podcast guids, not transcript text or download counts, and it covers all of OP3 with newest-first ordering. This prevents a common misinterpretation of what 'recent transcripts' means.

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 compact and front-loaded: what the tool returns comes first, followed by when to use it and what to do with the output. Every sentence earns its place, and there is no repetition of schema or annotation 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?

With only two optional, fully documented parameters and strong annotations, the definition covers selection, invocation, and output chaining. It states the output shape enough for an agent to pass podcast guids to show tools, so nothing critical is missing.

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 already describes both parameters fully, including the default and cost caveat for resolve_shows. The description adds no parameter-level detail beyond what the schema provides, so the baseline score of 3 applies.

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 identifies the exact resource: recently published OP3 episodes that carry a podcast:transcript tag, newest first. It also states the operational purpose of finding machine-readable podcasts and implicitly distinguishes itself from download-focused sibling tools. This leaves no ambiguity about what the tool returns or why it exists.

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?

It clearly says to use this tool when the goal is reading transcripts or finding machine-readable episodes, and contrasts it with counting downloads. It also tells the agent that the returned podcast guids can be passed to the show tools. However, it does not name a specific sibling tool as the alternative, so the guidance is clear but not fully explicit.

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