Preview favoriting a track

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

The description frames this as a 'Preview' (implying a non-mutating dry run), yet annotations declare readOnlyHint=false, so the agent cannot tell whether state actually changes. Nothing is said about whether a preview must be followed by a commit, whether it expires, or what the preview returns beyond the existence of an output schema.

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 front-loaded sentence with zero padding and no repetition of the title. It is efficient, though the brevity is partly under-specification rather than pure economy.

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-value explanation is not required. But for a preview/write-intent tool in a preview+commit architecture, the description omits the most decision-relevant context: how this pairs with tidal_commit_action and what the agent is expected to do after previewing.

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 the burden. It adds only 'one or more tracks', which conveys plurality and maps loosely to minItems=1, but says nothing about the maxItems=500 ceiling, the fact that entries are TIDAL track IDs, or any ID format.

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: 'Preview saving ... tracks to My Collection.' An agent can distinguish it from tidal_preview_unfavorite_track and tidal_list_favorite_tracks by the verb alone. It does not, however, distinguish itself from the near-twin tidal_preview_favorite_track_by_isrc, which differs only in the identifier type accepted.

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 at all. The critical routing question for a tool named 'preview' in a server that also exposes tidal_commit_action and ~30 other tidal_preview_* tools — namely whether this stages a change that must later be committed, and how — is left entirely unstated.

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