reorderPlaylistItems

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the core operation but omits details about side effects (e.g., permanent modification of playlist order), permissions (e.g., ownership or collaboration rights), or failure modes (e.g., invalid range boundaries). This is insufficient for a mutation tool with no annotation support.

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 a single, concise sentence that is front-loaded with the verb and resource. It contains no filler or redundant information, earning the highest score for structure.

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 tool with 5 parameters and no annotations, the description is adequate but incomplete. The schema explains all parameters, but the description does not mention important contextual aspects like the return value (e.g., updated snapshot ID) or preconditions. Given the tool's mutational nature, a bit more context would be valuable.

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 input schema covers 100% of parameters with descriptions, so the baseline is 3. The description does not add additional meaning beyond the schema; it only refers abstractly to 'range' and 'new position,' which are already elaborated in the parameter descriptions. The schema sufficiently defines each parameter's semantics.

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 clearly states the action ('Reorder'), the object ('a range of tracks within a Spotify playlist'), and the specific change ('moving them to a new position'). This distinguishes it from sibling tools like addTracksToPlaylist or removeTracksFromPlaylist, which perform different operations on playlist tracks.

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?

The description implies when to use the tool—when you need to manually reorder tracks within a playlist. It does not explicitly name alternatives or provide exclusion criteria, but the context is clear given the tool name and description. A score of 4 reflects this clear context without explicit exclusions.

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