reorder_playlist_items

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

No annotations are present, so the description must disclose mutation behavior. It only says 'Move', implying mutation, but does not mention whether the operation is reversible, requires ownership, or how indices shift. This is insufficient given 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 short sentence, which is concise and front-loaded. However, it is so terse that it omits important guidance, though conciseness itself is high.

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 4 parameters and no annotations or output schema, the description is minimal. It does not explain the semantics of 'range' or 'insert_before', nor the effect on playlist order. An agent would struggle to use it correctly without reading the schema further.

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 covers 100% of parameter descriptions, so baseline is 3. The description adds no parameter-specific detail beyond the schema, so it does not elevate.

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 'Move' and resource 'items within a playlist', clearly distinguishing it from siblings like add_to_playlist or remove_from_playlist. It also includes the concept of a 'range', matching the range_start and range_length parameters.

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 guidance on when to use this tool versus alternatives such as add_to_playlist or remove_from_playlist. It does not state conditions or prerequisites (e.g., ownership, playlist modification rights).

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