playlist_add

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

With no annotations, the description carries the full burden. It usefully discloses auto-resolution of names, implicit deduping, and internal chunking up to Spotify's 10k ceiling, but omits key mutation behavior: whether tracks are appended to the end, ordering guarantees, partial-failure handling, and required auth scope.

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 tightly written sentences that front-load the action, then the resolution/dedupe/chunking behavior and the capacity limit. Every clause earns its place and nothing is padded.

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 mutation tool with no annotations and no output schema, the description covers the batch mechanics reasonably well but leaves gaps: no return/confirmation semantics, no error behavior on unresolvable names, and no permission requirements. Adequate but not complete.

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 only 33% and the description does not compensate. The items semantics it describes are already in the schema's parameter description; 'dedupes' is ambiguous against the boolean dedupe parameter (is dedupe always on, or opt-in, and what is its default?), and playlist_id goes unexplained anywhere.

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 ('Bulk-add songs ... to a playlist') and adds meaningful scope detail (name/URI auto-resolution, dedupe, 10k ceiling, chunking). It is easily distinguished from mutation siblings like playlist_remove, playlist_reorder, or playlist_empty, though it never explicitly contrasts an alternative.

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?

There is no explicit when-to-use or when-not-to-use guidance. 'Bulk-add' and the 10k ceiling imply this is the tool for large batch insertions, but the description never tells the agent when to prefer this over, say, searching/resolving first, nor what happens if the playlist is at capacity.

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