playlist_reorder

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

No annotations are provided, so the description carries the full behavioral burden. 'Move' implies a mutation, but the description omits whether this requires auth/scopes, how positions are indexed (0-based vs 1-based), whether insert_before is absolute or relative, and what happens to surrounding tracks. For a mutation tool with zero annotation coverage this is a significant gap.

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 well-sized for the literal content, though the content itself is thin rather than the structure being at fault.

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 no annotations, no output schema, and four parameters at 0% schema coverage, the description should clarify indexing, permissions, and ordering semantics. It does not, leaving an agent unable to call the tool confidently beyond the basic intent.

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% and there are four parameters, three required. The description vaguely gestures at 'range' and 'new position' but never names or explains playlist_id, range_start, range_length (optional), or insert_before. It does not compensate for the schema's lack of descriptions, leaving insert_before and range semantics opaque.

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 ('Move') and resource ('a track (or range)') and the effect ('to a new position in a playlist'). This clearly distinguishes it from siblings like playlist_add, playlist_remove, and playlist_empty. It stops short of naming an alternative, but the purpose is unambiguous.

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 prerequisites, and no mention of when an agent should prefer playlist_add/remove or vice versa. The description only says what the tool does, not when to select it over the many sibling playlist_* tools.

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