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

Annotations only declare read-only/non-destructive/open-world; the description adds substantial behavior beyond that: the modal auto-loads further track pages, programmatic paging uses nextOffset, the tool issues no media URLs and no transcript text, and selecting a track hands off to the website-owned player under normal access limits. It also warns that catalog totals are not verified runtimes and must not be used to rank listening length — a real misuse guard.

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 core capability and the 'does not issue media URLs / transcript text' limits are front-loaded, and most sentences carry distinct information. A few trailing directives ('keep accompanying prose brief', 'Format durations in hours/minutes/seconds') are output-style instructions that dilute focus slightly but are not wasteful enough to hurt much.

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 an output schema present, return shape need not be described; the description instead covers what an agent must know to call it correctly — ID provenance, pagination mechanics, handoff to the player, and what is deliberately not returned. Nothing material is missing for a 3-parameter read-only catalog tool.

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 coverage is 0%, so the description must carry the load; it explains that specialId is an ID returned by other Comedy Buff tools and clarifies the roles of trackOffset, trackLimit, and the returned nextOffset for paging. It does not restate the numeric bounds/defaults (max trackLimit 20, default 10) that live in the schema, so it is good but not exhaustive.

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 concrete verb and resource: 'Open a special's track list using an ID returned by Comedy Buff tools', and enumerates the payload (comedians, tracks in catalog order, listening links, transcript availability/links). It also draws the boundary against siblings by declaring it 'does not issue media URLs or retrieve transcript text', which separates it from get_comedy_video and get_comedy_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?

Gives usable context: specialId comes from other Comedy Buff tools, model-driven inspection should use trackOffset/trackLimit with returned nextOffset, and titles are clues for a remembered bit rather than proof of content. It lacks an explicit 'use X instead when...' routing statement for discovery (e.g., search_comedy_specials), so it is strong but not complete.

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