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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context — result ordering (newest first) and the nature of the filters — but says nothing about pagination behavior or result size despite a limit parameter existing.

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?

A single front-loaded sentence covering verb, resource, ordering, and filters with zero filler. Tag examples earn their place by clarifying filter granularity.

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 5-parameter, zero-schema-coverage, no-output-schema list tool, the description should at minimum address the limit/pagination parameter and hint at the result shape. It covers filtering well but leaves the collection-size dimension unaddressed.

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 0%, so the description carries the burden; it explains from/to as a date range and gives concrete tag examples ('btc', 'stablecoins', 'nfts'), which is genuinely helpful. However, it omits the limit parameter (default 20, max 100) entirely, leaving one of five parameters undocumented anywhere.

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+resource ('List ATC shows') with ordering ('newest first') and the filterable dimensions, which is more than a tautology. It does not explicitly distinguish itself from siblings like search or get_episode, but 'List' vs. single-item/free-text search makes the intent reasonably clear.

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 word 'optionally filtered' implies how to narrow results, but there is no guidance on when to prefer this over search, search_transcripts, or topic_timeline, nor any exclusions. Usage is inferable rather than stated.

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