vibo_delete_song_comment

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

The description explicitly discloses the confirm-gating behavior ('Confirm-gated'), which goes beyond the annotations that only state readOnlyHint=false. It also clearly indicates a destructive action ('Delete'), and there is no contradiction with the annotations. It does not detail the preview behavior when confirm is false, but the input schema fills that gap.

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: two short sentences (or fragments) that clearly state the action and the gating behavior. Every word earns its place, with no fluff or repetition of the tool name.

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?

For a simple delete tool with fully described parameters, the description is nearly complete. It clearly states the action and a key behavioral constraint, while the rich input schema covers parameter details. The lack of an output schema is acceptable for a delete operation, and the preview behavior is documented in the confirm parameter.

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 description coverage is 100%, so the baseline is 3. The description itself adds no additional parameter-level semantics beyond what the schema already provides. The confirm-gated note relates to the confirm parameter but is already explained in the schema's parameter description.

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 a specific verb and resource ('Delete a comment on a song') that clearly distinguishes this from sibling tools like vibo_delete_section_comment, which deletes a section comment. The additional 'Confirm-gated' note immediately conveys a key purpose-relevant behavior.

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 provides no guidance on when to use this tool versus alternatives such as vibo_delete_section_comment or vibo_comment_on_song. The only usage-related hint is 'Confirm-gated,' which is behavioral rather than contextual. No exclusions or alternative recommendations are mentioned.

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