split_playlist

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

Annotations only declare destructiveHint=false, so the description carries most of the behavioral burden. It usefully discloses the quota footprint (1 GET + N POST /me/playlists + N POST items) and that new playlists are created, but says nothing about whether the source playlist is left intact, what happens on partial failure, or how dry_run interacts with the quota.

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?

Two front-loaded sentences with no filler; the core operation comes first and the quota cost second. The '(new playlists)' parenthetical is slightly redundant but harmless, and the terse quota shorthand is efficient.

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?

With five parameters, no output schema, and minimal annotations, the description covers the operation and its cost but omits important context: whether the source playlist survives, ordering of items across chunks, and what a dry_run report actually returns. Adequate but with clear gaps for a mutation-style tool.

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 all five parameters including name_prefix defaults and the dry_run preview semantics. The description adds no syntax or behavioral nuance beyond what is in the schema, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb and resource ('Split a playlist into N chunks') and immediately clarifies the output form ('new playlists'), which distinguishes it from siblings like merge_playlists, playlist_union, or playlist_trim. An agent can identify the operation without opening the schema.

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 when-to-use guidance, prerequisites, or named alternatives among the many playlist-manipulation siblings (merge_playlists, playlist_trim, copy_playlist). The quota note hints at cost but does not say when splitting is the right choice over manual item manipulation.

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