vibo_reorder_songs

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

Annotations provide readOnlyHint=false, so the write nature is known. The description adds 'Confirm-gated', which is a behavioral trait beyond the annotation, but this is also described in the schema's confirm parameter. No additional side effects, reversibility, or permission requirements are disclosed.

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 immediately states the purpose and a key trait. It is not a tautology and contains no unnecessary words, though it could be slightly more informative without losing efficiency.

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 mutation tool with a confirmation flow, 5 parameters, and no output schema, this description is under-specified. It lacks guidance on the preview/confirm workflow, target placement semantics, and does not reference sibling tools or edge cases, leaving the agent to infer critical 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 description coverage is 100%, so the baseline for parameter semantics is 3. The description adds no extra meaning beyond what the schema already provides; it does not explain the relationship between sourceSongIds and targetSongId or the preview behavior beyond the schema.

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 states a specific verb ('Reorder') and resource ('songs within a section'), making the primary action clear. However, it does not distinguish itself from the sibling tool 'vibo_move_song', which likely performs a similar single-song operation, so it lacks explicit differentiation.

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 is provided on when to use this tool versus alternatives like 'vibo_move_song' or 'vibo_remove_song_from_section'. The confirm-gated behavior is hinted but not explained as a usage prerequisite, and there is no mention of prerequisites or context.

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