Preview adding folder items

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing about what a preview produces, how long it stays valid, or how it is committed, which is the key behavioral fact for this family of tools.

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 efficient sentence with the action front-loaded and no wasted words. It is well-structured but arguably too terse given the missing workflow context.

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 re-explained, but for a preview tool sitting alongside tidal_commit_action, omitting the preview-to-commit lifecycle leaves a material gap an agent needs to call it 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?

Schema coverage is 0%, so the description carries some burden; it usefully clarifies that item_trns holds playlist or folder TRNs (not arbitrary IDs). It does not explain folder_id, its format, or the 500-item limit beyond what the schema encodes.

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 clear verb (preview adding) and resource (playlist or folder TRNs to a folder), which distinguishes it from siblings like tidal_preview_move_items_to_folder and tidal_preview_remove_folder_items. However, it does not clarify what 'preview' means relative to the sibling tidal_commit_action, leaving the commit-model implicit.

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, no mention that a preview must be committed separately (tidal_commit_action is a sibling), and no exclusions versus the other folder-mutating previews. The agent must infer the workflow entirely.

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