vibo_toggle_song_like

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

Annotations show readOnlyHint=false (writes). Description adds that the tool is 'confirm-gated', meaning it returns a preview unless confirm=true. However, missing details on response format, side effects (e.g., does it affect other users?), or permission requirements.

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?

Single sentence with two key pieces of information (action and confirm-gating). No filler, every word earns its place.

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 full schema coverage and no output schema, description provides the essential context: action and gate behavior. It omits expected behavior on failure, but for a simple toggle with confirm-gate, this is near-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?

Schema coverage is 100% with clear descriptions for all parameters. The description adds no new parameter information beyond what schema already provides (e.g., 'like/unlike' mirrors the liked param description). Baseline 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?

Description clearly states 'Like or unlike a song in a section' with a specific verb and resource. It distinguishes from sibling tools like vibo_add_song_to_section (adds song) and vibo_update_song (edits details). The 'Confirm-gated' qualifier adds precision.

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?

No explicit when-to-use or when-not-to-use guidance. The phrase 'Confirm-gated' implies a two-step process (preview then confirm) but does not compare to alternatives or specify prerequisites (e.g., user must be in event).

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