export_profile_state

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add value by flagging the artist-watchlist path quirk (cwd-relative, not ~/.spotify-mcp/) and noting the archive is schema-versioned, but it does not disclose other behavioral aspects such as whether the operation touches source data, disk write side effects, size implications beyond include_history, or idempotency.

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 the primary action front-loaded and the quirk note placed second, where it reads as an intentional caveat rather than clutter. It is compact and every sentence earns its place, though the parenthetical in the second sentence is slightly dense.

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 tool with three fully-documented optional parameters and no output schema, the description is largely complete: it states the data scope, the output format, and the one genuine path quirk. Its main gap is the absence of cross-references to related tools (import_profile_state, sidecar_export_bundle), which matters given the enormous sibling list.

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 baseline is 3; the schema already documents output_dir, include_history, and response_format clearly, including the enum. The description adds no parameter syntax or format details beyond the schema, though the artist-watchlist path quirk marginally enriches understanding of what data gets archived.

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 states a specific verb ('Export') with an enumerated resource — the exact sidecar stores (scenes, genre-tags, playback-ext, search-history, mutations, artist-watchlist) — and a concrete output (a single schema-versioned JSON archive). This level of specificity clearly differentiates it from the many sibling export tools that target playlists, libraries, snapshots, or listening history.

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 guidance on when to use this tool versus alternatives. The description never mentions that import_profile_state is the restore counterpart, nor does it differentiate itself from the similarly-named sidecar_export_bundle or the other export siblings. The path-quirk note is useful but is not usage guidance.

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