update-playlist

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

Discloses key behaviors: updates document fields, does not add/remove tracks, and is GM-only. With no annotations, description carries full burden and covers essential traits. Could mention idempotency or error conditions, but sufficient for typical use.

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?

Two sentences, front-loaded with action and scope. No redundant information. Every sentence adds value.

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?

Adequately covers tool purpose and constraints for a low-complexity tool (4 params, no nested objects, no output schema). Could mention return value or confirm action, but not essential given the context.

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 100% with good parameter descriptions. Description adds context by naming the fields (rename, playback mode, crossfade) but does not provide additional semantic detail beyond what schema already offers. Baseline 3 is appropriate.

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?

Description clearly states the tool updates playlist fields (rename, change playback mode, set crossfade) and explicitly excludes adding/removing tracks. Also notes GM-only restriction. Distinguishes from sibling tools like create-playlist or delete-playlist.

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?

Provides context on what the tool does and what it does not do (add/remove tracks). Implies it's for modifying existing playlists. No explicit alternative sibling mentioned, but the exclusion helps guide usage.

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