get_watch_later

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

No annotations are provided, so the description must disclose behavioral traits. It mentions using yt-dlp and reading cookies from a local browser, which is a key behavioral detail. However, it does not explain caveats like cookie availability, browser being closed, or failure scenarios. Some value is added, but it is not comprehensive.

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 a single, efficient sentence that is front-loaded with the action and resource, then specifies the method. No redundant or filler content.

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 list-retrieval tool, the description covers what it does and how (yt-dlp, local browser cookies). It lacks information about return format or error conditions, but given no output schema, it is reasonably complete. It could explicitly note that browser cookies must exist and the profile must match, which is only implied.

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 schema already documents limit, browser, and profile adequately. The description itself adds no additional parameter information, so it relies on the schema, giving a baseline score of 3.

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 the action ('Returns videos') and the specific resource ('your YouTube Watch Later list'), also mentioning the method (yt-dlp with cookies). This distinguishes it from the sibling tool get_subtitles, which is about subtitles, not watch later.

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 provides clear context: it is for retrieving Watch Later videos. However, it does not explicitly mention when to use this tool instead of alternatives or any exclusions. Given the only sibling is get_subtitles, the distinct purpose is clear, but explicit guidance is missing.

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