import_playlist

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

With no annotations, the description carries the full burden and discloses several non-obvious behaviors: appends rather than replaces, skips non-Spotify lines, dedupes only within the batch, commits in batches of 100, and dry_run=true avoids writing. It doesn't address partial-failure behavior or what the call returns, which keeps it from a 5.

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 sentences with no filler: purpose, source modes, and behavior details each get exactly one sentence, and the inverse relationship is front-loaded. Every clause earns its place.

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 5-parameter mutation tool with no output schema and no annotations, the description covers purpose, both input sources, and the key behaviors (skip, dedupe, batching, dry-run). The only real gap is the absence of any mention of the success result or failure semantics, which an output schema would otherwise cover.

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 baseline is 3. The description adds relational meaning beyond the schema by framing content and input_path as mutually exclusive document sources and by flagging dry_run=true as a preview mode, which nudges it to a 4.

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+resource: parses an M3U or CSV document and appends its Spotify URIs to a target playlist. The phrase 'the inverse of export_playlist' anchors it against a sibling, and it is clearly distinguishable from add_to_playlist or batch_add_to_playlist because it operates on parsed documents rather than raw track lists.

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 inverse-of-export_playlist relationship frames when this tool is appropriate, and the content-vs-input_path options tell the agent how to supply the document. It doesn't give explicit exclusions (e.g., when to prefer add_to_playlist for raw URIs), so it stops short of full when/when-not routing.

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