vibo_move_song

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

The description reveals the confirm-gating behavior, which is beyond the annotations (only readOnlyHint=false). It implies a two-step process (preview then confirm). However, it does not detail whether the operation is destructive, if order is affected, or other side effects, which would be valuable.

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. The key purpose is front-loaded, and every word contributes meaning 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?

Given no output schema and moderate complexity (5 parameters), the description is minimal. It covers the core action and confirm gate but lacks details on return values, error states, or ordering implications. It is adequate but could be more informative.

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%, so the schema already describes all parameters. The description adds value by explaining the confirm parameter as a gate ('confirm-gated'), clarifying its role beyond the schema's 'Must be true to proceed' description.

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 verb 'Move' and the resources 'songs from one section to another'. It distinguishes the tool from siblings like vibo_add_song_to_section and vibo_remove_song_from_section by specifying moving as a combined operation.

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 mentions 'Confirm-gated', indicating that a confirm parameter is required to execute the move. However, it does not provide explicit guidance on when to use this tool versus alternatives like add+remove, nor does it mention any prerequisites or when not to use it.

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