copy_playlist

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

With no annotations, the description carries the safety burden, and it does disclose useful behavior: order preservation, batching in groups of 100, and a dry-run mode that only reports. However, it does not state whether the source playlist is modified, what happens on partial failure, or any permission/ownership requirements.

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?

Three short sentences with the main purpose front-loaded, followed by the two most decision-relevant behaviors (batching and dry-run). No filler or repeated schema 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?

No output schema or annotations exist, and the description does not state what the tool returns, how max_results applies to a copy operation, or what limits/errors occur during the batched copy. This is insufficient context for a mutating tool with eight parameters.

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 coverage is 100%, so the schema already documents all eight parameters. The description adds a little context for dry_run and the batching behavior, but it does not clarify ambiguous parameters such as max_results in the copy flow; this lands at the baseline.

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 operation ('Duplicate an existing playlist into a new playlist') with the resource and result clearly stated, and adds the concrete constraint 'preserving track order.' It does not explicitly differentiate itself from sibling clone/duplicate tools such as playlist_clone_live, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance is given, and no alternatives are mentioned despite many adjacent siblings (create_playlist, add_to_playlist, playlist_clone_live, import_playlist). The only implied usage is the purpose itself; there is no guidance to help an agent choose between this and similar tools.

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