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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds behavioral context by explaining the meaning of 'live' and 'awaiting', and notes that it lists the 'real state' of episodes, which goes beyond what annotations provide.

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 two sentences long, front-loaded with the primary action, and every clause adds meaning—order, state definitions, and filtering use case. No filler or redundancy.

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?

Given there is no output schema, the description does a good job explaining what the tool returns qualitatively (episodes with their states). It also covers the main behavioral nuance (live vs awaiting) and provides a practical use-case example. It doesn't detail output fields, but for a list tool with this scope it's reasonably complete.

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 only 50%, so the description helps compensate by explaining the status enum values ('live' and 'awaiting') and their semantic differences. It does not add meaning for limit or pagination, but the core filtering parameter is clarified, which is valuable.

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 starts with a specific verb and resource: 'List a publisher's episodes', and provides additional scope ('newest-first', real state). This clearly distinguishes it from sibling tools like list_podcasts, publisher_stats, and publisher_status, which address different resources or aspects.

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 explicit usage guidance by showing how to filter with status=live or status=awaiting to answer the question 'what is still pending?'. While it doesn't list alternatives to avoid, the context clearly implies this is the tool for listing episodes with these states, and the sibling list further contextualizes its niche.

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