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

Annotations already declare readOnly/destructive/openWorld, so the bar is lower. The description still adds real context beyond them: page size (up to 100), the next_cursor round-trip, and the auth requirement (user's Cotlet API key with access to this app). It does not describe ordering guarantees beyond newest-first or error behavior.

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 first two sentences overlap heavily ('newest first, with status, release date' restated), so there is measurable redundancy. The pagination and auth notes are useful and front-loaded, but the opening could be tightened to one sentence.

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?

No output schema exists, and the description compensates by naming the returned fields (status, release date, ad count). For a zero-required-param filtered list tool this is largely complete, though it never states what a page's response envelope looks like beyond the cursor.

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 100%, so baseline is 3. The description adds meaning on top: it spells out the cursor/next_cursor pagination contract and the practical cap of 100 episodes per page, which helps the agent use limit and cursor correctly.

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 and resource (lists episodes of one show), plus scope details (newest first, one show only, status/release date/ad count). It is easily distinguished from libsyn_get_episode (single episode) and libsyn_list_shows (shows instead of episodes).

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?

Explains when the filters apply ('Filter by status or match titles with search') and gives pagination workflow. It does not explicitly name the get_episode alternative for fetching a single episode, so it stops short of full when-not guidance.

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