vibo_reorder_songs

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

The description reveals a key behavioral trait: 'Confirm-gated' indicates that the tool returns a preview unless the confirm parameter is true. This goes beyond the annotations (readOnlyHint: false) by explaining the two-step execution model. However, it doesn't fully describe what happens upon confirmation or any potential side effects.

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 extremely concise with two short sentences, front-loading the purpose and a key behavioral note. Every phrase adds value without redundancy.

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?

The description omits critical contextual information: what the preview returns, what exactly happens after confirmation, any permissions or prerequisites (e.g., ownership or editing rights), and how the reordering affects the section. Given no output schema, the description should compensate but fails to do so.

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 coverage is 100% with descriptions for all parameters. The description does not add extra meaning beyond the schema; the 'confirm-gated' hint relates to the confirm parameter but doesn't elaborate beyond what the schema already says. Baseline 3 is appropriate.

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 songs' and the resource 'within a section'. It distinguishes from siblings like vibo_add_song_to_section or vibo_move_song by focusing on reordering. However, it doesn't explicitly clarify that reordering changes the order of songs, which is implied but could be more explicit.

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 provides no guidance on when to use this tool versus alternatives like vibo_move_song or any other sibling. It only mentions 'confirm-gated' without explaining the workflow or prerequisites. There is no explicit context for appropriate usage.

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