yt_info

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

With no annotations, the description carries the full burden of disclosing behavior. It adds one nuance ('explicit playlist' implies the playlist flag must be set), but does not mention rate limits, authentication, error handling, output format, or side effects. Minimal beyond what the schema already shows.

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?

A single sentence that is front-loaded with the action and resource. Every word is useful, and it is immediately clear what the tool does without excessive detail.

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?

The tool is simple and has an output schema, reducing the need to explain return values. However, with no annotations and minimal description, it lacks guidance on edge cases (e.g., invalid URLs, playlist behavior with max_entries). It is adequate but not comprehensive.

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 compensate. It only alludes to the 'playlist' parameter with 'explicit playlist' and completely omits url and max_entries semantics. This is insufficient for a 3-parameter tool with no schema descriptions.

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 tool returns yt-dlp metadata for a video or explicit playlist. It uses a specific verb ('Return') and resource ('yt-dlp metadata'), and distinguishes it from siblings like yt_download and yt_subtitles by focusing on metadata retrieval.

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 the tool is for fetching metadata when you have a video or playlist URL, but it does not explicitly state when to prefer this over siblings (e.g., use yt_download for downloading, yt_subtitles for subtitles). No when-not-to-use conditions or alternatives are mentioned.

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