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

Annotations already cover the read-only/idempotent/non-destructive profile, yet the description still adds real behavioral context beyond them: the transcript is omitted by default with only has_transcript and transcript_length shown, paging is required for long transcripts, and an { error } is returned for an unknown id.

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 dense sentences with no filler; the core scope and the key default (transcript omitted) are front-loaded. The field enumeration is long but earns its place because there is no output schema to describe return values.

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 carries the full return-value burden and does so by listing the fields returned, the date_status states, the transcript default, and the error case. An agent has everything needed to call it correctly and interpret the result.

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 the baseline is 3, but the description adds meaning by tying the three transcript parameters together (default omission, include_transcript=true, and paging a long transcript). This clarifies how the parameters interoperate beyond the individual schema 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 states a specific verb and resource ('Full detail for one podcast episode') and enumerates the returned fields, so the agent knows exactly what it retrieves. The only gap is that it never names search_podcasts as the contrasting sibling, so sibling differentiation is implied rather than explicit.

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 gives useful mechanics for the transcript ('OMITTED by default ... pass include_transcript=true and page a long one'), which guides how to call the tool. However, it never states when to prefer this over search_podcasts or when not to use it, so tool-selection guidance is only implied.

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