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

With no annotations, the description carries the full behavioral burden and does so: it discloses that listing itself consumes no credits, that transcription costs 1 credit per episode, that repeat fetches are free, and that the key must have sufficient balance. It also reveals the return shape (id, title, date) and ordering.

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?

Four dense sentences, front-loaded with the core scope before routing, return fields, and the credit warning. No filler; every clause conveys a distinct actionable fact.

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 single-parameter list tool with no output schema, the description supplies the missing pieces an agent needs: return fields, ordering, the follow-up tool, and cost implications. Nothing required to invoke or sequence it correctly is absent.

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% and the schema already explains that podcast_id is the show id from a search_podcasts result, so the description merely restates it. No added syntax, format, or constraint detail beyond the schema, so the baseline 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?

States a specific verb (list) and resource (a podcast's back-catalog) with explicit scope: 'entire back-catalog (every episode, newest first)'. It is clearly distinguishable from siblings like list_new_episodes and search_podcasts, and it names the required identifier's origin.

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?

Gives explicit routing: 'Pass a podcast_id from a search_podcasts result', names get_transcript as the follow-up for any episode, and states the use case ('transcribe a whole show'). It also warns to verify credits before looping, which is actionable when-to-use guidance.

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