sync_playlist

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), it discloses that matching runs in the background, that external services (MusicBrainz, Soulseek) are contacted, and that side effects are gated behind yes=True. This is exactly the extra context annotations cannot convey.

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 dense, front-loaded sentences with no filler; the accepted-input parenthetical is long but earns its space by defining the required target parameter. The workflow instruction is placed last, which is the right order.

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 no output schema, the description correctly covers lifecycle (background job, status polling), safety gating, and next steps. The remaining gap is the semantics of lossy and min_confidence, which an agent would have to guess at.

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 0%, so the description must carry parameter meaning. It covers target well (valid input forms) and mentions yes=True, but says nothing about lossy or min_confidence (default 0.85), leaving two of four parameters undocumented in either place.

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 (sync/import) and resource (playlist) and enumerates accepted target forms (Spotify export, CSV, M3U, JSPF, XSPF, share URL, existing playlist id). It also names the downstream pipeline stages (resolve on MusicBrainz, diff, match on Soulseek), which clearly separates it from status and queue_downloads.

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?

Explicitly states the condition for the destructive path (nothing is downloaded unless yes=True, which the user must have asked for) and the required follow-up sequence (status(playlist_id) until finished, then queue_downloads). The alternatives in the workflow are named, not implied.

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