vibo_get_section_songs

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

The description adds context about the fields returned (like counts, flags, comments) beyond the readOnlyHint annotation, but does not disclose any behavioral traits such as pagination defaults or rate limits. The annotation already declares it as read-only, so the description provides moderate added 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 concise, consisting of two sentences that directly convey the tool's purpose and key capabilities without unnecessary words. Information is front-loaded.

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 lack of output schema, the description lists key returned fields (flags, comments, streaming links) but does not specify the structure of the response (e.g., array of objects, pagination info). It is mostly complete but could be slightly more detailed for a 9-parameter tool.

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?

With 67% schema description coverage, the description mentions sorting options but does not add meaning for undocumented parameters like sortDirection, isMustPlay, or q (though q is described in schema). The description does not fully compensate for missing schema descriptions.

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 what the tool does: it lists songs in a section with details like who added each, like counts, flags, comments, and streaming links. It also mentions sorting options. This distinguishes it from sibling tools like vibo_add_song_to_section or vibo_list_sections.

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 does not explicitly state when to use this tool versus alternatives. It implies usage for viewing songs in a section but lacks guidance on when not to use it or how it compares to other tools like vibo_get_playlist_songs or vibo_list_section_song_ideas.

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