vibo_remove_song_from_section

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

The description adds the 'Confirm-gated' behavior, which is not fully captured by annotations (readOnlyHint=false indicates mutation but not the guard). However, it does not disclose other traits like irreversibility, permissions, or side effects. With annotations already indicating mutation, the description adds moderate value.

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, using only two words and a hyphenated phrase. It is front-loaded with the action. While efficient, it is slightly too brief; a touch more context (e.g., a short sentence) would be ideal without becoming verbose.

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 the simplicity of the tool, the description covers the core action and the confirm gate. However, it lacks information about return values (no output schema) and any limitations or consequences of removal. It is adequate but not fully complete.

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 has 100% schema description coverage, so the parameters are already well-documented. The description adds no additional meaning beyond what the schema provides for the parameters, earning the baseline score of 3.

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 and resource: 'Remove one or more songs from a section.' It uses a specific verb (remove) and identifies the target (songs from a section). This directly distinguishes it from sibling tools like vibo_add_song_to_section or vibo_move_song.

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 usage for removing songs, but provides no explicit guidance on when to use this tool versus alternatives (e.g., vibo_move_song) or any prerequisites. The 'Confirm-gated' hint is helpful but does not fully substitute for usage direction.

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