vibo_get_playlists

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

Annotations provide readOnlyHint=true, and the description adds behavioral context: it requires a connected source and is a precursor to importing. There is no contradiction. The description adds value beyond annotations by explaining the dependency.

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 concise with two sentences, front-loading the action and purpose, followed by a prerequisite. No unnecessary words or details.

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 tool's simplicity and good schema descriptions, the description covers purpose, prerequisite, and connection to other tools. It lacks output format details but no output schema exists, so this is acceptable.

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 description adds minimal value beyond schema descriptions. It reinforces the source parameter's requirement but does not elaborate on 'q', 'skip', or 'limit'. Baseline of 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 tool lists playlists from connected streaming services (Spotify or Apple Music) for the purpose of importing songs. It distinguishes this from siblings like vibo_get_playlist_songs and vibo_import_playlist_to_section by focusing on the playlist listing itself.

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 specifies a prerequisite (source must be connected, see vibo_get_me) but does not explicitly state when to use this tool versus alternatives for listing or importing playlists. It implies usage context but lacks exclusion guidance.

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