vibo_add_song_to_section

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

The description reveals the confirm-gating behavior, which is critical for understanding the tool's two-step process. Annotations indicate readOnlyHint=false, consistent with a mutating operation. However, it does not disclose any potential side effects, permissions required, or edge cases like duplicate detection.

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 short sentences to convey the essential information. It is front-loaded with the action and avoids any extraneous detail.

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 adequately covers the core usage but lacks information on return values, error handling, and prerequisites like user permissions. Given the absence of an output schema and limited annotations, more detail could improve completeness for an agent.

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 description adds value by explaining that songUrl from vibo_search_songs is required and that viboSongId/title/artist should be included when known. This supplements the schema descriptions, which cover 71% of parameters. The lack of description for 'title' and 'artist' in the schema is partially mitigated by the tool description's suggestion to include them.

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 the verb 'Add' and noun 'song to a section', making the action clear. It also references the source tool vibo_search_songs, which distinguishes the intended input. However, it does not explicitly differentiate from related tools like vibo_import_playlist_to_section.

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 advises to pass a song from vibo_search_songs and notes the confirm-gating, but lacks explicit guidance on when to use this tool versus alternatives such as vibo_move_song or vibo_remove_song_from_section. The agent must infer from the name and context.

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