Find which episodes have transcripts

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful non-obvious traits: it does not fetch transcript files, it scans only recent episodes, and it reports both transcripts and chapters. The final heuristic about shows is useful, though slightly over-generalized; it does not contradict 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 sentences with distinct jobs: core function, usage direction, and decision heuristic. The most important information is front-loaded, and there is no filler.

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?

For a simple two-parameter discovery tool with strong annotations, the description covers scope, side effects, and when to call it. It does not specify the exact response shape, but no output schema is present and the description's 'report which...' gives enough of a contract for an agent to decide next steps.

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%, with both show and max already explained in the input schema. The tool description adds no parameter-level detail beyond 'recent episodes', so the 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?

The description states a specific verb and resource: 'Scan a show's recent episodes and report which of them publish a transcript or chapters'. It also distinguishes the tool from siblings by saying it does this 'without fetching any of the files' and by naming get_transcript/search_transcript.

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?

The description gives an explicit when-to-use rule: 'Call this before get_transcript or search_transcript on an unfamiliar show', with the rationale that it is 'one request' versus discovering the answer through a 'failed lookup per episode'. This makes the choice between tools clear.

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