list_episodes

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

No annotations are provided, so the description must carry behavioral disclosure. It usefully states that output is compact summaries and lists the fields, but it does not mention default behavior without filters, ordering/pagination, or that the detailed=true parameter can also return full objects while telling the agent to use get_episode for full objects. That nuance is left implicit.

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?

Two sentences with no filler. The most important information (compact summaries and fields) is front-loaded, and the alternative tool reference is placed at the end without 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?

For a list endpoint with 9 optional parameters and no output schema or annotations, the description covers the summary fields, filter axes, and a routing hint to get_episode. It is largely complete, though the no-filter default behavior and the detailed return option are only inferable from the schema.

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%, so the baseline of 3 applies. The description adds a helpful mental grouping of filter types (series, season, episode file), but does not describe parameter combination behavior or clarify detailed relative to get_episode beyond the schema.

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 clearly states a specific verb and resource: 'List episodes as compact summaries' and enumerates the exact fields returned. It also explicitly contrasts with get_episode ('Use get_episode for the full object'), which differentiates it from the sibling tool.

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 tells the agent when to use this tool (list episodes compactly) and explicitly routes full-object needs to get_episode. It also summarizes filter dimensions (series, season, episode file), making the main usage choice clear.

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