list_series

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

No annotations are provided, so the description carries the burden of behavioral disclosure. The verb 'List' clearly indicates a read-only operation, but the description does not mention pagination, ordering, error behavior, or any practical constraints. It provides the core behavior but lacks depth.

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 compact and front-loaded with the core purpose. The Args section is minimal and directly adds value by clarifying the accepted identifier formats. Every sentence earns its place with no redundant filler.

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 simple one-parameter list operation, the description is largely complete: it states what is listed, the scope, and the accepted parameter format. The presence of an output schema covers return-value expectations. Minor gaps include lack of explicit read-only confirmation and absence of edge-case behavior, but these are not critical for a straightforward list call.

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?

The schema only provides the parameter name and type, while the description adds that channel_id is a 'Channel UUID or slug.' This is meaningful semantic information that fully compensates for the 0% schema description coverage and is sufficient for an agent to supply the correct value.

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 states a specific verb ('List') and resource ('video series (batches)') scoped to a specific channel, clearly distinguishing it from sibling tools like list_channels and get_series_details. The parenthetical '(batches)' adds helpful domain context without ambiguity.

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 implies that the tool requires a specific channel and lists all series within it, but it does not explicitly mention when to prefer this over related tools or when not to use it. Usage context is present but only at an implied level; no alternatives or exclusions are named.

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