Preview favoriting a video

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is partially covered. The description adds nothing, however, about the defining behavior of a preview tool: that nothing is persisted until a subsequent commit, what the preview response represents, or whether repeat calls accumulate. For a mutation-adjacent tool this is a meaningful gap.

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 short sentence with the action front-loaded and zero filler. It is well formed, though its brevity is partly under-specification rather than 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 values need not be explained. However, for a preview tool sitting alongside tidal_commit_action and a large preview_* family, the description omits the preview-to-commit workflow that an agent must understand to use it correctly, leaving the definition incomplete for its complexity.

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?

Only one parameter exists and the schema description coverage is 0%, so the description carries the burden; 'one video' confirms single-item semantics but does not clarify whether video_id is a TIDAL numeric ID, a URL, or a URN (maxLength 160 hints at a URL/form but is not explained). The parameter name is largely self-explanatory, so this lands at an adequate baseline.

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 and resource ('Preview saving one video to My Collection'), which cleanly distinguishes it from tidal_preview_unfavorite_video and tidal_preview_favorite_track in the sibling list. It stops short of explaining what a 'preview' actually produces, so it is clear but not fully self-contained.

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 when-to-use guidance: nothing says this must be followed by a commit step, nothing explains how it differs from the real favoriting operation, and no prerequisites (auth, ownership of the collection) are mentioned. The agent must infer usage entirely from the name.

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