Preview favoriting an artist

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

Annotations give readOnlyHint=false, idempotentHint=false, destructiveHint=false, but the description doesn't resolve the tension between 'Preview' (sounds non-mutating) and readOnlyHint=false, nor explain what the preview produces or how long it stays valid. It adds 'one or more artists' and 'My Collection' but nothing about the staged-action lifecycle.

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?

A single tight sentence with the action front-loaded and no filler. It is efficient, though there is room for a second sentence that would have added needed context without bloat.

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?

An output schema exists so return values need not be described, but for a preview tool the essential context — that it stages rather than performs the change and requires a commit step — is absent. Given a paired tidal_commit_action sibling, this omission leaves the agent unable to use the tool correctly.

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?

One parameter with 0% schema description coverage. The schema conveys cardinality (minItems 1, maxItems 500) and array-of-strings type, but the description only restates 'one or more artists' and never clarifies that these must be TIDAL artist IDs, which is the key semantic the agent needs.

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 (preview saving) and resource (artists) with the target collection named, which cleanly separates it from tidal_preview_favorite_track/album/video siblings. It does not, however, explicitly contrast itself with tidal_preview_unfavorite_artist or tidal_commit_action.

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?

No when-to-use guidance beyond the implied 'preview' semantics. Critically, it never mentions that a preview must be followed by tidal_commit_action to actually apply the change, even though that sibling exists — an agent could reasonably assume calling this favorites the artist.

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