playlist_refresh

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

With no annotations, the description carries the transparency burden. It clearly states the behavior — forcing a playlist repaint — and frames it as a follow-up to bulk edits. This is adequate for a zero-parameter UI-refresh command, though it does not describe return behavior or error cases.

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?

The description is two short fragments with no wasted words. The core action, 'Force playlist repaint,' is front-loaded, followed by the single most relevant usage note.

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?

For a zero-parameter, no-output refresh command, the description fully covers purpose and timing. Nothing about the tool's invocation is left ambiguous, and no additional return-value or parameter detail is required.

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?

The tool has zero parameters and the schema confirms an empty properties object, so the baseline is 4. The description adds the situational context of 'after bulk edits,' which is useful but parameter documentation is not needed here.

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?

The description uses a specific verb ('repaint') and resource ('playlist'), and immediately states the intended use case. This distinguishes it from the sibling playlist editing tools like playlist_place_pattern and playlist_delete_clip, which perform data-changing operations rather than a UI refresh.

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?

It explicitly says when to use the tool: after bulk edits. There are no sibling refresh tools, so an alternative or when-not-to-use note is less necessary, but the guidance lacks an explicit exclusion or clarification about when a refresh is unnecessary.

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