diff_playlists

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: paging is internal/full, rendered rows are capped, and totals remain accurate regardless of the cap. It does not explicitly state whether the tool is read-only, and the schema's dry_run parameter ('describe exactly what would change without performing it') creates ambiguity about side effects that the description leaves unresolved.

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 sentences with no filler; the main action is front-loaded and the paging/cap caveats are packed efficiently. Every clause adds discriminative information.

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?

It covers the essential result categories, full paging, and total accuracy despite no output schema. It falls short by not clarifying the dry_run parameter's relevance to a compare operation and by not routing around sibling diff tools, so a completely self-sufficient definition would need slightly more.

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 baseline is 3; the description adds extra meaning to max_results by specifying that the cap applies only to rendered rows while totals stay accurate. Other parameters rely on their already-detailed 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 opens with a specific verb ('Compare') and identifies the resource ('two playlists') plus the exact comparison dimensions: tracks only in A, only in B by track ID, and position differences. The 'fully paged' qualifier further separates it from lightweight diff siblings such as playlist_diff or diff_playlist_snapshots.

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 behavior implies use when an agent needs a complete, position-sensitive comparison of two playlists, including accurate totals. However, it never states when to prefer this tool over the many sibling diff/intersection tools (playlist_diff, playlist_symmetric_difference, diff_playlist_snapshots), nor does it give exclusions or prerequisites.

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