Preview folder rename

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

Annotations declare readOnlyHint=false and idempotentHint=false, so the description's 'Preview' framing leaves the agent unsure whether state is mutated or merely staged. The description adds nothing about what a preview produces, whether it expires, or that a separate commit is required. Output schema covers return values but not the workflow semantics.

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 no filler. It is efficient, though arguably terse to the point of under-specification rather than genuinely concise.

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?

With an output schema present, return values are covered, but the description omits the preview/commit relationship, parameter meaning, and any behavioral context for a tool whose annotations mark it as non-read-only and non-idempotent.

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% and the description names no parameters. The agent can only infer that folder_id identifies the target and title is the new name from the tool name and schema titles; no format, constraint, or collision behavior is explained.

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 ('renaming one playlist folder') with the 'Preview' qualifier, which distinguishes it from the create/delete/move folder siblings. However, it never distinguishes itself from the commit side of the workflow (tidal_commit_action), so the agent cannot tell whether calling this alone accomplishes anything.

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. In a toolset full of preview_* tools paired with commit tools, the description omits the crucial fact that this is a dry-run step that must be followed by a commit action to take effect.

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