list_sync_collection_episodes

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

The annotations already convey readOnlyHint, idempotentHint, and destructiveHint=false, and the description is consistent with them. However, the description adds no behavioral context beyond that, such as authentication needs, rate limits, response size implications, or payload characteristics.

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-loads the core purpose with 'Get episode collection.' The endpoint and argument list are easy to scan, though the 'available_on: Query parameter' line is essentially 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 read-only list endpoint with an output schema and annotations, the description is close to adequate: it lists all parameters and pagination behavior. The main gaps are lack of sibling differentiation, undefined 'available_on' semantics, and no note about the full-versus-minimal episode collection variants.

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 must carry parameter meaning. It does so for page and limit, including useful clamping/default behavior, and vaguely for extended. 'available_on: Query parameter' adds no semantic value beyond the property name, so compensation is only partial.

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 opens with a clear verb-resource pair, 'Get episode collection,' and lists the exact endpoint. It is understandable on its own, but it does not differentiate this from the closely related sibling list_sync_collection_minimal_episodes or clarify that this is the authenticated user's sync collection.

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?

No usage guidance is provided. The description does not say when to choose this over list_sync_collection_minimal_episodes, list_sync_collection_media, or other collection endpoints, nor does it state any context or prerequisites.

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