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

With no annotations, the description carries the full behavioral burden, and it delivers the most decision-relevant non-obvious trait: the credit model (1 credit on first fetch, free repeats, errors never charged). It omits auth requirements, rate limits, and whether transcripts can be unavailable for some episodes, so it is strong but not exhaustive.

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?

Two sentences, zero waste, and the highest-value facts (what you get, what to pass, what it costs) are front-loaded. Every clause 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?

With no output schema, the description still describes the return value (clean Markdown, real speaker names, timestamps), the input provenance, and the billing model. For a single-parameter fetch tool this is complete enough to invoke correctly without further exploration.

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?

There is a single parameter with 100% schema description coverage, and the schema already states it is the episode id returned by search_podcasts. The description repeats that fact rather than adding format, constraints, or edge-case behavior, so the baseline of 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?

The description gives a specific verb and resource ('Fetch a podcast episode's transcript') plus the output shape ('clean Markdown with real speaker names and timestamps'). It also distinguishes itself from the rest of the sibling set, none of which deal with transcripts, and names search_podcasts as the upstream source.

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 tells the agent exactly how to obtain the required input ('Pass an episode id from search_podcasts'), which is actionable routing guidance. It stops short of stating when not to use the tool or how it relates to list_episodes/list_new_episodes, so it is clear context without explicit exclusions.

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