Reorder Playlist Tracks

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

Annotations indicate non-read-only and non-destructive. Description discloses concurrency guard via snapshot_id and positional semantics, adding behavioral context beyond annotations.

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?

Well-structured with Args block, Returns, Note, and Example. Slightly lengthy due to detailed example, but all content is relevant and aids understanding.

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?

Complete description for a 5-parameter reorder tool: explains all params, return value, concurrency guard, and provides a helpful example. Output schema exists, so return details are covered.

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 description coverage is 0%, but the description explains all parameters (playlist_id, range_start, insert_before, range_length, snapshot_id) with clear semantics, default behavior, and usage note.

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?

Clear verb+resource: 'Move a contiguous block of tracks to a new position within a playlist.' Distinct from sibling tools like add_tracks_to_playlist or remove_tracks_from_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 example and explains zero-based positions, but does not explicitly state when to use this tool versus alternatives (e.g., when reordering vs. adding/removing).

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