youtube_save_track

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

With no annotations provided, the description carries the full burden for behavioral disclosure, but it only lists the intended operations. It fails to mention that 'mode' is preview vs apply, that playlists can be created via createIfMissing, the default privacyStatus, or what happens to duplicates.

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 entire description is a single efficient sentence with zero filler or repetition. It front-loads the resource and lays out the action sequence in a natural order.

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 9-parameter tool with no annotations, no output schema, and no per-parameter schema descriptions, this high-level sentence is insufficient to invoke the tool safely or effectively. Important behaviors such as preview mode, rule handling, and playlist creation are completely absent.

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?

Since schema description coverage is 0%, the description must compensate for 9 parameters, but it only loosely maps 'input' to 'Identify a YouTube song/video', 'dedupe' to 'deduplicate it', and 'playlist'/'category' to 'named or category playlist'. Parameters like mode, rules, prefix, privacyStatus, and createIfMissing remain unexplained.

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 names a specific resource and a sequence of distinct actions ('Identify a YouTube song/video, classify it, deduplicate it, and add it to a named or category playlist'). This multi-verb structure clearly distinguishes it from sibling tools like youtube_identify_track, youtube_classify_playlist, and youtube_add_to_playlist.

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 gives no explicit guidance on when to use this composite tool versus composing individual sibling calls, nor does it mention mode semantics or conditions like already-identified tracks. Usage context is only implied by the action list, with no alternatives or exclusions.

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